-
-
Notifications
You must be signed in to change notification settings - Fork 532
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
v11 beta #2077
Comments
I just tried the beta together with SWC and it works great, thank you! |
What's new in this version? |
I haven't had time to prepare release notes yet. They will accompany the v11 stable release. Until then, the commit log will have to suffice. It links to PRs which describe their changes, though their descriptions will not be as easy to read as documentation. |
I generally hate adding "me too" type comments, but I think that with a beta they have some value. I'd also run into issue with incompatibilities caused by changing swc behavior, simply upgrading from 10.9.1 to the new beta was seamless and worked perfectly. Thank you. |
Works good here with regards to #2000 as well. |
Works great, however when I specify "ts-node": {
"swc": true,
"transpileOnly": true,
"experimentalSpecifierResolution": "node",
"moduleTypes": {
"../**/*": "mjs"
}
} I'm getting this error:
The solution for me was to patch-package ts-node, and add a fallback for when |
@cspotcode Would it be worth doing a sweep through the repo and remove any dead code or tech debt for v11 release? Some examples that come to mind would be:
|
Is this package still being maintained? @cspotcode |
Looks like maintenance is a problem. #1907 is an easy merge that hasnt been done for almost two years. |
v11 beta has been published to npm.
https://www.npmjs.com/package/ts-node/v/11.0.0-beta.1
npm install ts-node
will not give you the beta by default.You must do
npm install ts-node@beta
to install the beta tag.I haven't had time to prepare release notes yet. They will accompany the v11 stable release. Until then, the commit log will have to suffice. It links to PRs which describe their changes, though their descriptions will not be as easy to read as documentation.
v10.9.1...v11.0.0-beta.1
The text was updated successfully, but these errors were encountered: