Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
[NPM] better publish and docs
See original GitHub issuefeature request
Please concider using semantic-release and commitizen
For automatic documentation, versioning and npm releasing.
More info here: https://github.com/semantic-release/semantic-release https://github.com/commitizen/cz-cli
Issue Analytics
- State:
- Created 7 years ago
- Comments:7 (4 by maintainers)
Top Results From Across the Web
npm-publish - npm Docs
Publishes a package to the registry so that it can be installed by name. By default npm will publish to the public registry....
Read more >sindresorhus/np: A better `npm publish` - GitHub
Why. Interactive UI; Ensures you are publishing from your release branch ( main and master by default); Ensures the working directory is clean...
Read more >How to publish packages to npm (the way the industry does ...
There are more steps. We'll go through what steps are required, and I'll show you an easy way to publish and update your...
Read more >Control What you Publish Inside your Npm Packages - Medium
You don't want to publish temporal files and make your package weigh 300 tons of gigabytes or, even worse, put private files in...
Read more >npm packages in the Package Registry - GitLab Docs
You need an token to publish a package. There are different tokens available depending on what you're trying to achieve. For more information,...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
the project is now using lerna, good enough for now. I want to stabilize that state a bit before going forward (i still have a hack to workaround issue with symlink & also i had to put gl-react in a devDep of some packages because the peerDep wouldn’t install it… (FYI it’s a progress, it was even more hacky before^^) )
the granularity of releases can be improved later, in fact lerna allows to chose between fixed/locked mode or independent. (there is even
lerna-semantic-releaseif we need more)Facebook tried to keep same version numbers, but it all failed when they had a breaking change in react and could not match it in time with react-native. They stoped doing it after that.
I still think that keeping version numbers between repos will be pretty hard to do in the long run. As i wrote in my last 2 posts.
Lets say you release a bugfix in
gl-react-nativethat fixes issues related to Android. Causing a new release: 12.1.2 -> 12.2.0. Then you need to release a blank version forgl-react-dom. the “web” people will ask, what is fixed in this version?I think version numbering, keeping version notes, and change log is a big deal. Breaking changes occours, and will then automaticly be updated. Depending packages will also be set in peerDeps as of nodejs 6.