8000 Update Getting-started.md by mauriceKA · Pull Request #9297 · loopbackio/loopback-next · GitHub
[go: up one dir, main page]
Skip to content

Update Getting-started.md #9297

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 1 commit into from
Jun 2, 2025
Merged

Update Getting-started.md #9297

merged 1 commit into from
Jun 2, 2025

Conversation

mauriceKA
Copy link
Contributor

without an additional npm i, you will get an error: https://stackoverflow.com/questions/72181423/loopback-cli-lb-clean-command-not-found-linux

Just documentation update.

Come on guys, the link https://loopback.io/doc/en/contrib/code-contrib.html does not work. How am I supposed to follow this?

Checklist

  • DCO (Developer Certificate of Origin) signed in all commits
  • npm test passes on your machine
  • New tests added or existing tests modified to cover all changes
  • Code conforms with the style guide
  • API Documentation in code was updated
  • Documentation in /docs/site was updated
  • Affected artifact templates in packages/cli were updated
  • Affected example projects in examples/* were updated

👉 Check out how to submit a PR 👈

@mauriceKA
Update Getting-started.md
a256ee2 
without an additional npm i, you will get an error:
https://stackoverflow.com/questions/72181423/loopback-cli-lb-clean-command-not-found-linux

Signed-off-by: mauriceKA <post@patrik-spiess.de>
@dhmlau
Copy link
Member
dhmlau commented Feb 25, 2023

@mauriceKA, thanks for the PR. However, there's no need to run npm i after creating the LB app. I wonder if disabling some options in the prompt would lead to that. Could you please let me show me how to reproduce the problem? I'd also like to see if you run lb4 app_name --yes (--yes means accepting all defaults) would give the same result. Thanks.

@dhmlau
Copy link
Member
dhmlau commented Feb 25, 2023

Also, thanks for your feedback on the "contributing code" docs. I agree that there's room for improvement. Would you be interested in helping us to improve that side of the documentation as well?

@muhme
Copy link
Contributor
muhme commented Aug 9, 2023 •
edited
Loading

I had the same problem also on the very first run, before "npm start" the command "npm install" was needed as there was the error "sh: lb-clean: command not found". Found the solution (run npm install before) in the already named https://stackoverflow.com/questions/72181423/loopback-cli-lb-clean-command-not-found-linux

I am on macOS Ventura 13.4.1, node v20.3.1, npm 9.8.1 and following the Getting-Started documentation step by step w/o changing anything

however, I am not able to reproduce the problem:

  • three more new apps are created and there is no need to run "npm install"
  • Even with fresh node installation with docker run -it --entrypoint /bin/bash node (with node v20.5.0) does not have the problem
  • Even after brew uninstall npm && brew install npm does not have the problem

therefore sorry, this is just for information

@dhmlau dhmlau merged commit 3bc01eb into loopbackio:master Jun 2, 2025
@dhmlau
Copy link
Member
dhmlau commented Jun 2, 2025

@mauriceKA, sorry about the delay. This PR should've merged long time ago. Thanks again for your contribution! 👍

@dhmlau dhmlau mentioned this pull request Jun 2, 2025
Closed
8 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@dhmlau dhmlau dhmlau approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@mauriceKA @dhmlau @muhme
0