Conversation
| "url": "https://github.com/bytecodealliance/jco/issues" | ||
| "url": "https://github.com/nomicfoundation/jco/issues" | ||
| }, | ||
| "homepage": "https://github.com/nomicfoundation/jco#readme", |
There was a problem hiding this comment.
If we're going to expose our fork as the landing site of the package, it would be good to add information to the readme exposing that this is a fork from bytecodealliance, and what are the reasons for it. This is to help lost souls that got this package to know where to place issues.
There was a problem hiding this comment.
I would like to avoid any unnecessary edits/changes to upstream files if possible.
I added a note about this in the homepage. WDYT?
ggiraldez
left a comment
ggiraldez
left a comment
There was a problem hiding this comment.
Looks good to me.
Re: this comment adding one or two lines at the top of the README.md file wouldn't hurt. Maybe pointing to a new file (FORK.md?) where we can describe the purpose of the fork, what changes it introduces, and why we don't want to merge them upstream?
3 participants
package.jsonURLspublishConfigtopackage.json.npmrcfile