-
Notifications
You must be signed in to change notification settings - Fork 9
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
An in-range update of ts-node is breaking the build 🚨 #44
Comments
Version 3.0.6 just got published.Your tests are passing again with this version. Explicitly upgrade to this version 🚀 Release NotesCache FixFixed
|
Version 3.1.0 just got published.Your tests are passing again with this version. Explicitly upgrade to this version 🚀 Release NotesCombine Source Map and Content CacheChanged CommitsThe new version differs by 6 commits.
See the full diff |
Version 3.2.0 just got published.Your tests are passing again with this version. Explicitly upgrade to this version 🚀 Release NotesBoolean Env FlagsChanged
Added
CommitsThe new version differs by 13 commits.
See the full diff |
Version 3.2.1 just got published.Your tests are passing again with this version. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 18 commits.
There are 18 commits in total. See the full diff |
Version 3.2.2 just got published.Your tests are passing again with this version. Explicitly upgrade to this version 🚀 Release NotesImprove Source Map Inline PerfFixed
CommitsThe new version differs by 20 commits.
There are 20 commits in total. See the full diff |
Version 3.3.0 just got published.Your tests are passing again with this version. Explicitly upgrade to this version 🚀 Release NotesValidate Cache FilesChanged
CommitsThe new version differs by 22 commits.
There are 22 commits in total. See the full diff |
Version 3.0.5 of ts-node just got published.
This version is covered by your current version range and after updating it in your project the build failed.
As ts-node is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.
I recommend you give this issue a high priority. I’m sure you can resolve this 💪
Status Details
Commits
The new version differs by 7 commits.
c18331a
3.0.5
5cf97b1
Add
--inspect-brk
to known flags (#343)7dfb3e3
Pin node tests at
6.x
(#340)633d537
chore(package): update chai to version 4.0.1 (#337)
b751a56
Define
exports
and improvegetTypeInfo
help (#332)d018300
Update
yn
default optioncc3bf22
Expose
_
bin file for consumers to useSee 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 🌴
The text was updated successfully, but these errors were encountered: