Skip to content
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

fix(frontend): npm localhost3000 not found #28

Merged
merged 12 commits into from
Aug 1, 2024

Conversation

YuanhuanO
Copy link
Collaborator

@YuanhuanO YuanhuanO commented Aug 1, 2024

Closes #

πŸ“‘ Description

βœ… Checks

  • My pull request adheres to the code style of this project
  • My code requires changes to the documentation
  • I have updated the documentation as required
  • All the tests have passed
  • Branch name follows type/descript (e.g. feature/add-llm-agents)
  • Ready for code review

β„Ή Additional Information

@YuanhuanO YuanhuanO requested a review from lwaekfjlk August 1, 2024 02:06
Copy link
Owner

@lwaekfjlk lwaekfjlk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

let me test on this branch before mering

@lwaekfjlk lwaekfjlk changed the title Bug/fix npm localhost3000 not found fix(frontend): npm localhost3000 not found Aug 1, 2024
@lwaekfjlk
Copy link
Owner

@YuanhuanO

(base) haofeiyu@haofeis-mbp gpu-bartender % npm start
npm error code ENOENT
npm error syscall open
npm error path /Users/haofeiyu/Desktop/gpu-bartender/package.json
npm error errno -2
npm error enoent Could not read package.json: Error: ENOENT: no such file or directory, open '/Users/haofeiyu/Desktop/gpu-bartender/package.json'
npm error enoent This is related to npm not being able to find a file.
npm error enoent

npm error A complete log of this run can be found in: /Users/haofeiyu/.npm/_logs/2024-08-01T02_16_07_918Z-debug-0.log

@lwaekfjlk
Copy link
Owner

how to solve this error?

@lwaekfjlk
Copy link
Owner

I think it is due to the removal of package.json?

Copy link
Owner

@lwaekfjlk lwaekfjlk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I failed to run npm when running npm start in the root folder. The error is included in the conversation. Looks like it is related to a path error.

@lwaekfjlk lwaekfjlk linked an issue Aug 1, 2024 that may be closed by this pull request
@YuanhuanO
Copy link
Collaborator Author

let me test on this branch before mering

I failed to run npm when running npm start in the root folder. The error is included in the conversation. Looks like it is related to a path error.

Please try to run under the frontend file because of the structure changes

@YuanhuanO
Copy link
Collaborator Author

let me test on this branch before mering

I failed to run npm when running npm start in the root folder. The error is included in the conversation. Looks like it is related to a path error.

Please try to run under the frontend file because of the structure changes

README.md was also modified as:

  1. Clone the repository:

    git clone git@github.com:lwaekfjlk/gpu-bartender.git
  2. Navigate to the root directory:

    cd frontend
  3. Install dependencies:

    npm install
  4. Build the project:

    npm run build
  5. Start the application:

    cd gpu-bartender
    npm start

@YuanhuanO YuanhuanO closed this Aug 1, 2024
@lwaekfjlk
Copy link
Owner

yeah, but the npm start is still at the root folder?

@YuanhuanO YuanhuanO reopened this Aug 1, 2024
@YuanhuanO
Copy link
Collaborator Author

yeah, but the npm start is still at the root folder?

yes

@lwaekfjlk lwaekfjlk merged commit 4dce5ac into main Aug 1, 2024
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[BUG]: duplicate package-lock.json
2 participants