[BUG] 2.5.5 broke semver
See original GitHub issueIn the release notes for 2.5.5 it says:
Updated React plugin to v3.0.0
This appears to be a semver violation, and broke our builds. We had been using 2.3.0, with our package.json
having:
"@microsoft/applicationinsights-react-js": "^2.3.0",
"@microsoft/applicationinsights-web": "^2.3.0"
Thus, npm install
now gives version 2.5.4 of applicationinsights-react-js
and version 2.5.5 of applicationinsights-web
.
Since it expects 3.0.0 of applicationinsights-react-js
, we are now failing with
TS2322: Type ‘ReactPlugin’ is not assignable to type ‘ITelemetryPlugin’
The error appears similar to #1032, but in this case the version mismatch is apparently by design.
Issue Analytics
- State:
- Created 3 years ago
- Comments:11 (4 by maintainers)
Top Results From Across the Web
What is semantic versioning? by Tamas Piros
If you are working with Node.js and npm packages it's likely that have heard the term "semver" or semantic versioning.
Read more >Repairable, Damaged, Salvage Volkswagen Beetle for Sale
Huge selection of Salvage, Repairable and Clean Title Volkswagen Beetle Auto Auction. Open to the public - FREE registration - Join ...
Read more >Help! Timing Belt broke...now what? | VW Beetle Forum
If I was only going 5 mph...is it possible it may be in the $3k range for repair? Does anyone have a shop...
Read more >Semantic versioning • jotaen.net
Although the SemVer specification only refers to bug fixes, ... release (e.g. from 2.5.4 to 2.5.5 ); You apply a refactoring to a...
Read more >My car loses power, the epc light comes on, then it loses most ...
2001 Volkswagen Beetle ... reads wrong it will throw codes for the throttle peddle, the epc, and your breaks don't want to work...
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
I believe that I addressed this as part of the 2.5.7 release. Simplistically, rather than the react and react native releases using the previous build number for the dependency, I split the publishing into 2 steps (release core, then release react/reactnative with updates to use the just release core)
So react 3.0.2 uses 2.5.7
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.