Applicationinsights-js: [BUG] React 3.1.1 does is not reusing the shims v2 module correctly -- causing __extends errors

[MSNev]

Description/Screenshot

Steps to Reproduce

• OS/Browser:
• SDK Version [e.g. 22]:
• How you initialized the SDK:

Expected behavior

Additional context
Add any other context about the problem here.

[MSNev]

I've deprecated v3.1.1 package until I can publish an updated version

[MSNev]

PR to fix this is #1555

[MSNev]

Reopening for tracking

[MSNev]

FYI - Internal prod build servers are timing out -- I need a good clean run to be able to release, will release as soon as I get a good run.

[MSNev]

Still having issues with the new tests on the internal servers -- still working on it

[MSNev]

Finally got a good build, however, the publish step is broken and will require an update -- unlike to get this fixed today now 😞 😭

[MSNev]

Publish step is broken

[sujitykulkarni]

Got socket timeout issue with fresh npm install attempt just now (28th APr 2021 21:20 IST).

npm ERR! request to https://registry.npmjs.org/@microsoft/applicationinsights-shims/-/applicationinsights-shims-2.0.0.tgz failed, reason: Socket timeout
Is it due to broken publish?

[MSNev]

@sujitykulkarni, no that is not due to the broken publish, that sounds like a network issue or a problem on the npmjs servers.

The publish issue is an issue in the way the production build servers prepare the tarball, and turns out that even though we have a pre-package step the publish was re-creating it without have full access to all of the packages (on the publish servers) the fix for this is in PR #1557

[MSNev]

PR is merged, back on the waiting for official internal build generation before publishing -- __hopefully__ this will complete within the next few hours (yes can take this long 😢 )

[MSNev]

Ok, finally published!!!

If there are still issues related to this please comment here and I'll jump on it.
For now closing this issue.