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

Many packages in package.lock are deprecated or otherwise not reccomended #438

Open
voidarclabs opened this issue Jan 13, 2025 · 0 comments

Comments

@voidarclabs
Copy link

To test changes locally, without docker installed, the official instruction is to run npm install and then npm run to start a server on port 3000. First of all, there is no longer an "npm start" script, instead being npm build and then npm dev to achieve the same effect. This being a docs issue, I will leave it at face value and continue with the subject matter.

When running aforementioned "npm install" command, it first gives the error that some packages are unable to be resolved:
image
Then, when running with --force (definitely not reccomended), it gives numerous warnings about deprecated packages:
image

This could be fixed by either changing the docs to match these changes, or updating the version numbers in package.lock. Thought this was issue worthy.

Cheers!

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

No branches or pull requests

1 participant