-
-
Notifications
You must be signed in to change notification settings - Fork 58
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
package.json is not generated ? #140
Comments
solved for now with copying the the unsolved / unknown problem was |
Getting the same error on Linux (Debian) following the install instructions from the docs. It's a blocking issue for getting started. |
From what I've pieced together it looks like this script is run in the On mac I get the error below, but on Debian it fails silently (hence no package.json is created) ➜ livesvelte_test_app mix live_svelte.setup
-- Installing npm dependencies...
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: undefined@undefined
npm ERR! Found: esbuild@0.16.17
npm ERR! node_modules/esbuild
npm ERR! dev esbuild@"^0.16.17" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer esbuild@">=0.17.0" from esbuild-svelte@0.9.0
npm ERR! node_modules/esbuild-svelte
npm ERR! dev esbuild-svelte@"*" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution. My theory is that esbuild is pinned to 0.16 in the setup script to prevent this issue (the |
@EricAndresen |
Wow! That was so fast. I was poking around the setup script and saw it change in realtime. Thanks man! Really excited about the project. |
hello, i'm trying to install in new fresh projects and got this instead


the package.json was not created then make the node said "Error: Cannot find module 'esbuild'"
is there any wrong things i've done ?
my environment :
The text was updated successfully, but these errors were encountered: