-
-
Notifications
You must be signed in to change notification settings - Fork 61
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
Vite Deno templates do not work #31
Comments
This is the whole console in text |
Hmm I also got that on deno 1.33.1 macos. Downgrading to 1.32.0 works, and I see 1.33.0 has stricter hoisting in |
Thanks for the ping. I will look into this issue ASAP. |
Opened a PR that fixes the problem. This fix will be released in Deno v1.32.2 later this week. Thanks for the report! |
This commit changes how paths for npm packages are handled, by canonicalizing them when resolving. This is done so that instead of returning "node_modules/<package_name>@<version>/node_modules/<dep>/index.js" (which is a symlink) we "node_modules/<dep>@<dep_version>/index.js. Fixes #18924 Fixes bluwy/create-vite-extra#31 --------- Co-authored-by: David Sherret <[email protected]>
This commit changes how paths for npm packages are handled, by canonicalizing them when resolving. This is done so that instead of returning "node_modules/<package_name>@<version>/node_modules/<dep>/index.js" (which is a symlink) we "node_modules/<dep>@<dep_version>/index.js. Fixes #18924 Fixes bluwy/create-vite-extra#31 --------- Co-authored-by: David Sherret <[email protected]>
👋 Not sure if this should be a new issue or not since I initially ran into this issue but it has since morphed into a similar issue from #9, in any case, since this is still Vite/Deno related presumably figured I'd start here : Upgrade to Deno resolved the esbuild error, but now I'm getting the following when I run
Not sure where to start debugging, still a little new to how Deno works. Let me know if I should put this in a new issue. |
@sortofsleepy thanks for the report. Would you mind opening an issue in the Deno repo? This looks like an internal error in Deno that should be fixed there. |
Closing as Deno 1.32.2 is released. |
When i try to create a deno + framework template it gives me this error when running the app.
I originally wanted to try react but after it not working i tried it for svelte too with the same error. Please tell me how to fix it and correct the issue.
deno: 1.33.1
node: 16.14.2
Os: Windows 10
The text was updated successfully, but these errors were encountered: