Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Snyk] Upgrade reflect-metadata from 0.1.12 to 0.1.13 #9

Merged
merged 1 commit into from
Feb 25, 2022

Conversation

snyk-bot
Copy link
Contributor

Snyk has created this PR to upgrade reflect-metadata from 0.1.12 to 0.1.13.

merge advice
ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.


  • The recommended version is 1 version ahead of your current version.
  • The recommended version was released 3 years ago, on 2019-01-15.
Release notes
Package name: reflect-metadata
  • 0.1.13 - 2019-01-15
  • 0.1.12 - 2018-01-16

    This release contains some bug fixes and test improvements. It addresses the following issues:

    • #80 - metadata seemingly erased when using multiple files with karma,mocha,webpack
    • #78 - Error when working with another polyfill, like core-js/reflect
    • #45 - When installed redundantly, Metadata could be erased

    This release also fixes a critical issue in 0.1.11 that prevents the library from loading.

from reflect-metadata GitHub release notes
Commit messages
Package name: reflect-metadata
  • aacaeb1 0.1.13
  • 5b98fe1 Do not generate source maps when publishing
  • c2dbe1d Add test to verify does not overwrite existing implementation

Compare


Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

🧐 View latest project report

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs

@bangbang93 bangbang93 merged commit 8f9ebad into master Feb 25, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants