Closed tylerbuchea closed 3 years ago
Here is an overview of what got changed by this pull request:
Issues
======
+ Solved 1
- Added 2
See the complete overview on Codacy
@loonydev I'd like to see this PR get merged given that it is a major fix.
Hi @asktree, you can merge it if you want. Comment lefts by Codacy app, which use my identities for a some reason. We will fix it soon.
@loonydev @tylerbuchea Hey guys! I've been away for a while. Sorry for ghosting. Today i've released a new version that supports React 16.8 and hooks by default.
Regarding your PR - using npm view
will not solve the issue, since it will return the version in the NPM registry, rather than the local one
Unfortunately, the issue you've raised is real, but there is no easy fix, due to various limitations in how VScode can interact with the codebase. This is why the decision was made to look to the future and support hooks-enabled React.
Thank you for being involved and for the PR
npm list react --version --depth=0
appears to return the version of the npm cli not the version of React. Maybe something changed in the npm API? I'm using npm:v6.14.4/node:v12.16.2 and all of these commands return the same value (the version of npm I'm using):This command seems to be a good alternative
npm view react version
. I tested it as far back as npm:v5.3.0/node:v8.4.0.