porsager / porsager/postgres-shift
Question: npm package update
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 56
- Forks
- 15
- PR merge metrics
- No merged PRs in 30d
Description
is the latest code updated in npm? Because when i install it from npm and check the code, it's different from what you have in github master.
I am particularly referring to this change. https://github.com/porsager/postgres-shift/commit/da61a6142c4aca097d0d1a091d4c0ea148468119
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing the npm package contents with the GitHub master revision and the referenced commit da61a6142c4aca097d0d1a091d4c0ea148468119. Confirm whether the published package is missing that change; done means the discrepancy is resolved or clearly documented with the package version involved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- release
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100