Add homepage and repository properties for published package.json files #1198
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi, this is my first contribution to this library, I checked the notes here: https://github.com/pikapkg/snowpack/blob/master/CONTRIBUTING.md and didn't see any special notes about submitting a PR without attached issue. Hope it's alright to submit this kind of PR? If there's anything I should change or this is the wrong process, please let me know, thanks.
Changes
This adds the
homepage
andrepository
settings to all of the package.json files.I added this because as I try to use the project, I keep searching for the plugins on Google, which leads to the NPM homepage. Then, when I want to check the source, I get stuck because there is no
repository
orhomepage
link to guide me to Github:The
esinstall
package already hashomepage
andrepository
set, which look like this on NPM:So I copied this format to all the other published package.json files that I could find.
Testing
(1)
I followed the
Tests
section here https://github.com/pikapkg/snowpack/blob/master/CONTRIBUTING.md#tests. Running the tests was successful and the snapshots did not seem to change when I ranyarn test -u
.(2)
I manually clicked the different homepage URLs to make sure they loaded a real page.
(3)
I tried making a new app locally:
And I confirmed that the new properties did not end up the package.json of the created project
I can run
npm run build
andnpm run start
in this directory, and they seem to work fine too.(4)
I also confirmed the package.json files were still valid by writing and running another script:
verify.js script to check package.json files
No errors were detected. Just for reference, here was the output:
output of > node verify.js
Docs
No documentation updated, this shouldn't require any change of user behavior. Just make it easier for users to browse through the plugins and understand how they work together.