Publish the react 16 compatible version to NPM
See original GitHub issueHi @clauderic!
I see you’ve updated this library’s peerDeps
to be compatible with react 16. Can you publish a version containing that change to NPM?
Issue Analytics
- State:
- Created 6 years ago
- Comments:5
Top Results From Across the Web
React v16.0 – React Blog
We're excited to announce the release of React v16.0! ... All compatible addons are published separately on npm, and have single-file ...
Read more >16.14.0 - react - npm
React is a JavaScript library for building user interfaces.. Latest version: 18.2.0, last published: 6 months ago. Start using react in your ...
Read more >The complete guide to publishing a React package to npm
So you want to publish a React component as a package to npm? This guide has all the information you need, even if...
Read more >Add support for node 16 (current release) and scss #11037
I start using node 16. My dependency node-scss require update to 6 version. When update this dependency and try build my app i...
Read more >Upgrading React version and it's dependencies by reading ...
To update to a new major version all the packages, install the npm-check-updates package globally: npm install -g npm-check-updates · Run the ...
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 FreeTop 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
Top GitHub Comments
It was due to not uninstalling react-sortable-hoc yet. All good here
On Thu, Mar 15, 2018, 02:04 Kieran Sedgwick notifications@github.com wrote:
@cyrus-za You’re mistaken. Perhaps you installed the wrong version? A fresh install of
npm install amo-react-sortable
has this in thepackage.json
:Let me know if I’ve overlooked something.
Edit: Just saw that I didn’t change the repository link in the
package.json
file. This doesn’t affect using the package, but does obscure where the code came from. It lives here