-
Notifications
You must be signed in to change notification settings - Fork 0
Update ts-node to the latest version 🚀 #66
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
base: master
Are you sure you want to change the base?
Conversation
Version 3.0.1 just got published.Update to this version instead 🚀 Release NotesSpecify EngineFixed
|
Version 3.0.2 just got published.Update to this version instead 🚀 Release NotesDiagnostic FilteringFixed
|
Version 3.0.3 just got published.Update to this version instead 🚀 CommitsThe new version differs by 6 commits0.
false See the full diff |
Version 3.0.4 just got published.Update to this version instead 🚀 Release NotesDefault Cache ModeFixed
|
Version 3.0.5 just got published.Update to this version instead 🚀 CommitsThe new version differs by 7 commits.
See the full diff |
Version 3.0.6 just got published.Update to this version instead 🚀 Release NotesCache FixFixed
|
Version 3.1.0 just got published.Update to this version instead 🚀 Release NotesCombine Source Map and Content CacheChanged |
Version 3.2.0 just got published.Update to this version instead 🚀 CommitsThe new version differs by 7 commits.
See the full diff |
Version 3.0.0 of ts-node just got published.
The version 3.0.0 is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of ts-node.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Release Notes
Remove LazyChanged
lazy
configuration option - will always loadtsconfig.json
file without waiting for first load to avoid issues with first-class (entry).js
filesCommits
The new version differs by 3 commits .
3def533
3.0.0
67eabed
Use
sha256
for hash algorithm9caa1c5
Remove
lazy
option for first-class.js
inputsSee the full diff.
Not sure how things should work exactly?
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 🌴