NPM package publishing issue
- Dominant language
- JavaScript
- Stars
- 48.7k
- Forks
- 2.5k
- PR merge metrics
- No merged PRs in 30d
Description
Hi,
I noticed that some code that is present in the repository in git commit tagged as 1.11.9 is not present in the npmjs package that as a library user I install in my node_modules.
Take a look for example this commit:
https://github.com/iamkun/dayjs/commit/fefdcd4b6b807786f65139b6dd801e0014d7dc6f
If package is installed locally with `npm i -S dayjs@1.11.9`, the code in `node_modules/dayjs/plugin/utc.js` does not include the changes from the commit.
Contributor guide
Research direction
Compare commit fefdcd4b6b807786f65139b6dd801e0014d7dc6f with the published dayjs@1.11.9 artifact, focusing on node_modules/dayjs/plugin/utc.js. Start by reproducing the issue with npm i -S dayjs@1.11.9; done means the npm package contains the reported changes from the tagged repository commit.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- release
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100