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 ts-node from 8.6.2 to 8.7.0 #2

Closed

Conversation

snyk-bot
Copy link

Snyk has created this PR to upgrade ts-node from 8.6.2 to 8.7.0.

ℹ️ 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 15 days ago, on 2020-03-02.
Release notes
Package name: ts-node
  • 8.7.0 - 2020-03-02

    Fixed

    • Remove buggy caching of ts.sys.readDirectory (#969)
    • Fix REPL ASI handling when user input starts with - (#944)

    Added

    Changed

    • Deprecate ts-script in favor of ts-node-script (#948) @G-Rath

    Docs

    • Fix bash syntax error in README (#943) @abraj
    • Add Github issue templates (#959, #965, #947)
    • Add IntelliJ debug instructions to README (#958)
    • Add mocha 7 usage example to README (#961)
  • 8.6.2 - 2020-01-13

    Fixed

    • Downgrade yn due to node engine (#942)
from ts-node GitHub release notes

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

@retorquere retorquere closed this Feb 11, 2022
@retorquere retorquere deleted the snyk-upgrade-c4800daea182c95cbca1eb6fbf026cbb branch April 12, 2022 17:34
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