reflect-metadata
0.2.2 · 29 Mar 2024Apache-2.068.7M / weekRepositoryHomepagenpmAtom feed
Upgrading reflect-metadata From 0.0.3 to 0.2.2
17 releases in betweennotes for 11
Reading releases, release notes and advisories…
- 1+
- change to make
- 0
- advisories fixed
- 2+
- new
- 2+
- fixes
Counted from 11 of 17 release notes. Advisories are counted from the advisory database, in full.
Before you upgrade
Tick each one off as you go- Breaking0.1.3
Release by release
0.2.2no release note
- Fixed
Fix stack overflow crash in isProviderFor
- Fixed
- New
Add /lite and /no-conflict exports
- New
- Fixed
Fix variable name
- Fixed
0.1.4 – 0.1.139 releases, nothing new or fixed; 4 without a note
- Breaking
Includes several minor, non-breaking changes to type information.
- Breaking
0.1.2no release note
- New
Add typescript.definition entry in package.json for tsd
- New
9 other lines we could not sort, mostly version bumps
- 0.2.0
No dynamic evaluation in
/litemode - 0.1.14
Bypass webpack
process.envinlining - 0.1.12
Metadata seemingly erased when using multiple files with karma,mocha,webpack
- 0.1.12
Error when working with another polyfill, like core-js/reflect
- 0.1.12
When installed redundantly, Metadata could be erased
- 0.1.10
Reflect.getMetadata return undefined only in IE11
- 0.1.10
Remove mentions of ES7 (we're already on ES9 for new features)
- 0.1.9
Library changes behaviour of property decorator
- 0.1.1
Incorrect environment detection in WeakMapPolyfill
1 internal line (docs, tests, tooling) left out.
A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.