-
-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Create-Svelte - Fixing sucrase issue while running build script #1000
Create-Svelte - Fixing sucrase issue while running build script #1000
Conversation
PR 1000!! Congrats! 😄 |
thanks — can you fix the lint errors please? (note that i just pushed a commit to this branch — we use uppercase sparingly in these parts :) FYI the reason this failed locally for you is probably that you're on an ancient version of Node. Since 12.20 or something like that, named imports from CommonJS modules are possible in the majority of cases |
I don't think there's anything that actually needs fixing here. If there was flakiness in some part of the automated build/publish, we should just try to run that again. Locally, on latest What's being changed in this PR does seem to just be something that's already supported in later versions of Node. |
I've opened #1001 to hopefully resolve the problem that was preventing the automatic publishes from happening. |
Working version is published now. Thanks for pointing out the issue |
Just a note for anybody else that follows me (also tag future self "mentioned" @delhanty): make sure you have at least the latest version of Node 14 installed. I ran into this Edit: looks like the minimum versions are
|
sveltejs#1000). See my comment sveltejs#1000 (comment) references >Node.js 14.13.0 added support for named CJS exports, see #35249 and this change has also been backported to Node.js v12.20.0. nodejs/node#32137 (comment) and >Yep, it was fixed after downloading 14.13.1, thank you nodejs/node#35249 (comment)
I was trying to run the
create-svelte
CLI locally but I was not able to do it with success. I realized that we got the #989 merged and, with this, we were not able to runnpm run build
in order to build thedist
folder (and then run the CLI to set a project).Tests
pnpm test
and lint the project withpnpm lint