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

Designate DevDependencies BE #200

Open
esparr opened this issue Nov 14, 2023 · 0 comments · Fixed by #180
Open

Designate DevDependencies BE #200

esparr opened this issue Nov 14, 2023 · 0 comments · Fixed by #180
Assignees

Comments

@esparr
Copy link
Collaborator

esparr commented Nov 14, 2023

Certain packages and libraries are only needed when actively developing the project, and are unnecessary when deployed. For example, testing suites are important to make sure covered code is behaving properly, but have no effect on how the project runs. These are known as DevDependencies.

DevDependencies should first be identified. If they are not already marked as such in the Pipfile or package.json, uninstall then reinstall the package using one of the following commands:

Backend: pipenv install --dev [package-name]

Frontend: npm install [package-name] --save-dev

@esparr esparr added this to Momentors Nov 14, 2023
@esparr esparr self-assigned this Nov 14, 2023
@esparr esparr converted this from a draft issue Nov 14, 2023
@esparr esparr linked a pull request Nov 14, 2023 that will close this issue
7 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: 🎭 Staging
Development

Successfully merging a pull request may close this issue.

1 participant