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

Specify project name attribute in package.json #591

Merged
2 commits merged into from
Mar 15, 2024

Conversation

ghost
Copy link

@ghost ghost commented Mar 15, 2024

npm will "randomly" change the package-lock.json file with the name attribute based on the local directory where the project is being built, this specifics a name in package.json to stop this behavior, see: npm/cli#2264

Also add proper license attribute.

letting npm use the directory name which can
randomly change the package-lock.json file, also
add proper license instead of UNLICENSED
@ghost ghost added dependencies Pull requests that update a dependency file low priority does not impact production code labels Mar 15, 2024
@ghost ghost self-assigned this Mar 15, 2024
@ghost ghost requested a review from melroy89 March 15, 2024 22:27
@ghost ghost merged commit 672e691 into main Mar 15, 2024
7 checks passed
@ghost ghost deleted the use_name_in_package_json_instead_of_directory_name branch March 15, 2024 23:18
andrewmoise pushed a commit to andrewmoise/mbin that referenced this pull request Mar 17, 2024
This pull request was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file low priority does not impact production code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant