run-llama/create-llama
1
0
Fork 0
mirror of https://github.com/run-llama/create-llama.git synced 2026-07-16 03:04:21 -04:00
Code Issues 39 Packages Projects Releases 10 Wiki Activity

React dependency installation error #111

New Issue
Closed
opened 2026-02-15 19:16:02 -05:00 by yindo · 5 comments
yindo commented 2026-02-15 19:16:02 -05:00
Owner
Copy Link
Copy Source

Originally created by @Superskyyy on GitHub (Dec 19, 2024).

Originally assigned to: @leehuwuj on GitHub.

When running the command npx create-llama@latest

Known workaround is to issue npm config set legacy-peer-deps true

Starting development servers

Installing frontend dependencies using npm. It might take a while...
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: my-app@0.1.0
npm error Found: react@19.0.0-rc-66855b96-20241106
npm error node_modules/react
npm error   react@"19.0.0-rc-66855b96-20241106" from the root project
npm error
npm error Could not resolve dependency:
npm error peer react@"^18.2.0 || 19.0.0-rc-de68d2f4-20241204 || ^19.0.0" from next@15.1.2
npm error node_modules/next
npm error   next@"^15.0.3" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /home/ubuntu/.npm/_logs/2024-12-20T02_27_23_332Z-eresolve-report.txt
npm error A complete log of this run can be found in: /home/ubuntu/.npm/_logs/2024-12-20T02_27_23_332Z-debug-0.log
Traceback (most recent call last):
  File "/home/ubuntu/Synthetic/my-app/run.py", line 75, in start_development_servers
    frontend_process, frontend_port = await _run_frontend()
                                      ^^^^^^^^^^^^^^^^^^^^^
  File "/home/ubuntu/Synthetic/my-app/run.py", line 141, in _run_frontend
    _install_frontend_dependencies()
  File "/home/ubuntu/Synthetic/my-app/run.py", line 199, in _install_frontend_dependencies
    run([package_manager, "install"], cwd=".frontend", check=True)
  File "/home/ubuntu/.pyenv/versions/3.12.8/lib/python3.12/subprocess.py", line 571, in run
    raise CalledProcessError(retcode, process.args,
subprocess.CalledProcessError: Command '['/home/ubuntu/.nvm/versions/node/v23.4.0/bin/npm', 'install']' returned non-zero exit status 1.

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/home/ubuntu/Synthetic/my-app/run.py", line 55, in dev
    asyncio.run(start_development_servers())
  File "/home/ubuntu/.pyenv/versions/3.12.8/lib/python3.12/asyncio/runners.py", line 194, in run
    return runner.run(main)
           ^^^^^^^^^^^^^^^^
  File "/home/ubuntu/.pyenv/versions/3.12.8/lib/python3.12/asyncio/runners.py", line 118, in run
    return self._loop.run_until_complete(task)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/ubuntu/.pyenv/versions/3.12.8/lib/python3.12/asyncio/base_events.py", line 686, in run_until_complete
    return future.result()
           ^^^^^^^^^^^^^^^
  File "/home/ubuntu/Synthetic/my-app/run.py", line 105, in start_development_servers
    raise SystemError(f"Failed to start development servers: {str(e)}") from e
SystemError: Failed to start development servers: Command '['/home/ubuntu/.nvm/versions/node/v23.4.0/bin/npm', 'install']' returned non-zero exit status 1.
Child process exited with code=1
Failed to run app: 1

Aborting installation.
Unexpected error. Please report it as a bug:
 1
Originally created by @Superskyyy on GitHub (Dec 19, 2024). Originally assigned to: @leehuwuj on GitHub. When running the command `npx create-llama@latest` Known workaround is to issue `npm config set legacy-peer-deps true` ``` Starting development servers Installing frontend dependencies using npm. It might take a while... npm error code ERESOLVE npm error ERESOLVE unable to resolve dependency tree npm error npm error While resolving: my-app@0.1.0 npm error Found: react@19.0.0-rc-66855b96-20241106 npm error node_modules/react npm error react@"19.0.0-rc-66855b96-20241106" from the root project npm error npm error Could not resolve dependency: npm error peer react@"^18.2.0 || 19.0.0-rc-de68d2f4-20241204 || ^19.0.0" from next@15.1.2 npm error node_modules/next npm error next@"^15.0.3" from the root project npm error npm error Fix the upstream dependency conflict, or retry npm error this command with --force or --legacy-peer-deps npm error to accept an incorrect (and potentially broken) dependency resolution. npm error npm error npm error For a full report see: npm error /home/ubuntu/.npm/_logs/2024-12-20T02_27_23_332Z-eresolve-report.txt npm error A complete log of this run can be found in: /home/ubuntu/.npm/_logs/2024-12-20T02_27_23_332Z-debug-0.log Traceback (most recent call last): File "/home/ubuntu/Synthetic/my-app/run.py", line 75, in start_development_servers frontend_process, frontend_port = await _run_frontend() ^^^^^^^^^^^^^^^^^^^^^ File "/home/ubuntu/Synthetic/my-app/run.py", line 141, in _run_frontend _install_frontend_dependencies() File "/home/ubuntu/Synthetic/my-app/run.py", line 199, in _install_frontend_dependencies run([package_manager, "install"], cwd=".frontend", check=True) File "/home/ubuntu/.pyenv/versions/3.12.8/lib/python3.12/subprocess.py", line 571, in run raise CalledProcessError(retcode, process.args, subprocess.CalledProcessError: Command '['/home/ubuntu/.nvm/versions/node/v23.4.0/bin/npm', 'install']' returned non-zero exit status 1. The above exception was the direct cause of the following exception: Traceback (most recent call last): File "<string>", line 1, in <module> File "/home/ubuntu/Synthetic/my-app/run.py", line 55, in dev asyncio.run(start_development_servers()) File "/home/ubuntu/.pyenv/versions/3.12.8/lib/python3.12/asyncio/runners.py", line 194, in run return runner.run(main) ^^^^^^^^^^^^^^^^ File "/home/ubuntu/.pyenv/versions/3.12.8/lib/python3.12/asyncio/runners.py", line 118, in run return self._loop.run_until_complete(task) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/ubuntu/.pyenv/versions/3.12.8/lib/python3.12/asyncio/base_events.py", line 686, in run_until_complete return future.result() ^^^^^^^^^^^^^^^ File "/home/ubuntu/Synthetic/my-app/run.py", line 105, in start_development_servers raise SystemError(f"Failed to start development servers: {str(e)}") from e SystemError: Failed to start development servers: Command '['/home/ubuntu/.nvm/versions/node/v23.4.0/bin/npm', 'install']' returned non-zero exit status 1. Child process exited with code=1 Failed to run app: 1 Aborting installation. Unexpected error. Please report it as a bug: 1 ```
yindo closed this issue 2026-02-15 19:16:02 -05:00
yindo commented 2026-02-15 19:16:02 -05:00
Author
Owner
Copy Link
Copy Source

@Superskyyy commented on GitHub (Dec 19, 2024):

After the workaround, the server still failes to start

Notice the log, next dev 3000 is missing a -p flag.

Starting development servers

Installing frontend dependencies using npm. It might take a while...
npm warn deprecated inflight@1.0.6: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
npm warn deprecated are-we-there-yet@2.0.0: This package is no longer supported.
npm warn deprecated npmlog@5.0.1: This package is no longer supported.
npm warn deprecated rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported
npm warn deprecated gauge@3.0.2: This package is no longer supported.
npm warn deprecated fs-promise@2.0.3: Use mz or fs-extra^3.0 with Promise Support
npm warn deprecated @aws-sdk/signature-v4@3.374.0: This package has moved to @smithy/signature-v4
npm warn deprecated @aws-sdk/protocol-http@3.374.0: This package has moved to @smithy/protocol-http
npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported

added 1130 packages, and audited 1131 packages in 1m

299 packages are looking for funding
  run `npm fund` for details

found 0 vulnerabilities

Waiting for frontend to start, port: 3000, process id: 65968

> 2@0.1.0 dev
> next dev 3000

Invalid project directory provided, no such directory: /home/ubuntu/Synthetic/2/.frontend/3000
Traceback (most recent call last):
  File "/home/ubuntu/Synthetic/2/run.py", line 75, in start_development_servers
    frontend_process, frontend_port = await _run_frontend()
                                      ^^^^^^^^^^^^^^^^^^^^^
  File "/home/ubuntu/Synthetic/2/run.py", line 161, in _run_frontend
    raise RuntimeError("Could not start frontend dev server")
RuntimeError: Could not start frontend dev server

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/home/ubuntu/Synthetic/2/run.py", line 55, in dev
    asyncio.run(start_development_servers())
  File "/home/ubuntu/.pyenv/versions/3.12.8/lib/python3.12/asyncio/runners.py", line 194, in run
    return runner.run(main)
           ^^^^^^^^^^^^^^^^
  File "/home/ubuntu/.pyenv/versions/3.12.8/lib/python3.12/asyncio/runners.py", line 118, in run
    return self._loop.run_until_complete(task)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/ubuntu/.pyenv/versions/3.12.8/lib/python3.12/asyncio/base_events.py", line 686, in run_until_complete
    return future.result()
           ^^^^^^^^^^^^^^^
  File "/home/ubuntu/Synthetic/2/run.py", line 105, in start_development_servers
    raise SystemError(f"Failed to start development servers: {str(e)}") from e
SystemError: Failed to start development servers: Could not start frontend dev server
Child process exited with code=1
Failed to run app: 1

Aborting installation.
Unexpected error. Please report it as a bug:
 1```
@Superskyyy commented on GitHub (Dec 19, 2024): After the workaround, the server still failes to start Notice the log, ` next dev 3000` is missing a `-p` flag. ``` Starting development servers Installing frontend dependencies using npm. It might take a while... npm warn deprecated inflight@1.0.6: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful. npm warn deprecated are-we-there-yet@2.0.0: This package is no longer supported. npm warn deprecated npmlog@5.0.1: This package is no longer supported. npm warn deprecated rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported npm warn deprecated gauge@3.0.2: This package is no longer supported. npm warn deprecated fs-promise@2.0.3: Use mz or fs-extra^3.0 with Promise Support npm warn deprecated @aws-sdk/signature-v4@3.374.0: This package has moved to @smithy/signature-v4 npm warn deprecated @aws-sdk/protocol-http@3.374.0: This package has moved to @smithy/protocol-http npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported added 1130 packages, and audited 1131 packages in 1m 299 packages are looking for funding run `npm fund` for details found 0 vulnerabilities Waiting for frontend to start, port: 3000, process id: 65968 > 2@0.1.0 dev > next dev 3000 Invalid project directory provided, no such directory: /home/ubuntu/Synthetic/2/.frontend/3000 Traceback (most recent call last): File "/home/ubuntu/Synthetic/2/run.py", line 75, in start_development_servers frontend_process, frontend_port = await _run_frontend() ^^^^^^^^^^^^^^^^^^^^^ File "/home/ubuntu/Synthetic/2/run.py", line 161, in _run_frontend raise RuntimeError("Could not start frontend dev server") RuntimeError: Could not start frontend dev server The above exception was the direct cause of the following exception: Traceback (most recent call last): File "<string>", line 1, in <module> File "/home/ubuntu/Synthetic/2/run.py", line 55, in dev asyncio.run(start_development_servers()) File "/home/ubuntu/.pyenv/versions/3.12.8/lib/python3.12/asyncio/runners.py", line 194, in run return runner.run(main) ^^^^^^^^^^^^^^^^ File "/home/ubuntu/.pyenv/versions/3.12.8/lib/python3.12/asyncio/runners.py", line 118, in run return self._loop.run_until_complete(task) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/ubuntu/.pyenv/versions/3.12.8/lib/python3.12/asyncio/base_events.py", line 686, in run_until_complete return future.result() ^^^^^^^^^^^^^^^ File "/home/ubuntu/Synthetic/2/run.py", line 105, in start_development_servers raise SystemError(f"Failed to start development servers: {str(e)}") from e SystemError: Failed to start development servers: Could not start frontend dev server Child process exited with code=1 Failed to run app: 1 Aborting installation. Unexpected error. Please report it as a bug: 1```
yindo commented 2026-02-15 19:16:03 -05:00
Author
Owner
Copy Link
Copy Source

@Superskyyy commented on GitHub (Dec 19, 2024):

image
I'm not sure why everyone else seem to be ok with running it, but the -- is necccesary and after adding it, it start to work. AFAIK the -- is necssary in NPM to make arg passing work.

@Superskyyy commented on GitHub (Dec 19, 2024): ![image](https://github.com/user-attachments/assets/083636c2-eda2-4271-adcb-da508e818c13) I'm not sure why everyone else seem to be ok with running it, but the `--` is necccesary and after adding it, it start to work. AFAIK the -- is necssary in NPM to make arg passing work.
yindo commented 2026-02-15 19:16:03 -05:00
Author
Owner
Copy Link
Copy Source

@Superskyyy commented on GitHub (Dec 19, 2024):

@leehuwuj https://www.npmjs.com/package/create-llama/v/0.2.17 using this version is fine, which dosn't go through the newer simplified logic. Can you help to take a look at these two issues?

@Superskyyy commented on GitHub (Dec 19, 2024): @leehuwuj https://www.npmjs.com/package/create-llama/v/0.2.17 using this version is fine, which dosn't go through the newer simplified logic. Can you help to take a look at these two issues?
yindo commented 2026-02-15 19:16:03 -05:00
Author
Owner
Copy Link
Copy Source

@myhendry commented on GitHub (Dec 21, 2024):

image I'm not sure why everyone else seem to be ok with running it, but the -- is necccesary and after adding it, it start to work. AFAIK the -- is necssary in NPM to make arg passing work.

for newbies like me, the code amended is inside the run.py file

@myhendry commented on GitHub (Dec 21, 2024): > ![image](https://private-user-images.githubusercontent.com/26076517/397597312-083636c2-eda2-4271-adcb-da508e818c13.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzQ3NjE4MjMsIm5iZiI6MTczNDc2MTUyMywicGF0aCI6Ii8yNjA3NjUxNy8zOTc1OTczMTItMDgzNjM2YzItZWRhMi00MjcxLWFkY2ItZGE1MDhlODE4YzEzLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDEyMjElMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQxMjIxVDA2MTIwM1omWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWE2N2JhNjA5Y2RkOWRjNWM5OTRmYTg2YzE4ZTJkYTYxOGI5NjNhY2YzNWRlN2U1NWQxNzhiMzZiNjQwNDQxYWEmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.1ULOEh6L6qUsj9ILWaZUIcUwDfX-qVNrwkSNQiBITHI) I'm not sure why everyone else seem to be ok with running it, but the `--` is necccesary and after adding it, it start to work. AFAIK the -- is necssary in NPM to make arg passing work. for newbies like me, the code amended is inside the run.py file
yindo commented 2026-02-15 19:16:04 -05:00
Author
Owner
Copy Link
Copy Source

@marcusschiesser commented on GitHub (Dec 26, 2024):

fixed in 0.3.24

@marcusschiesser commented on GitHub (Dec 26, 2024): fixed in 0.3.24
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
pull-request
Mirrored from GitHub Pull Request
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: run-llama/create-llama#111
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?