[Deprecation] SharedArrayBuffer will require cross-origin isolation as of M91, around May 2021

[cobrexus]

What version of Next.js are you using?

10.0.5

What version of Node.js are you using?

14.15.0

What browser are you using?

Google Chrome Version 90.0.4400.8 (Official Build) dev (64-bit)

What operating system are you using?

Windows 10

How are you deploying your application?

npm run dev (npx next dev)

Describe the Bug

I get this warning in the console:

scheduler.development.js:298 [Deprecation] SharedArrayBuffer will require cross-origin isolation as of M91, around May 2021. See https://developer.chrome.com/blog/enabling-shared-array-buffer/ for more details.

Expected Behavior

No warnings in the console

To Reproduce

Run npm run dev or npx next dev in the terminal in a Next.js project.

[ploxx95]

i have same bug

[achrizal15]

saya juga mengalami hal yang sama

[agektmr]

I'm not entirely sure how next.js works, but since it has dependency with React, this issue might be related: facebook/react#20829

[timneutkens]

Yep this is coming from React and has already been fixed (as linked above).

[gaearon]

17.0.2 is out with the fix. (But there was no real problem, it's a false positive.)

[iDVB]

@gaearon

17.0.2 is out with the fix. (But there was no real problem, it's a false positive.)

We are still seeing this error with 17.0.2 for react and react-dom. We've also restarted the dev server.

[gaearon]

It does not contain that code so something’s wrong on your side. Check where the log is coming from and manually inspect how that gets pulled into your bundle.

[baileymckay]

I'm still getting this too.

react and react-dom are both on 17.0.2. I'm using next.js (11.0.1--latest), so it could be some build artifact. newSharedArrayBuffer appears twice in the next.js build file, though the one Chrome flags (I assume the first instance) seems to be coming from node_modules/util.

I know it's just a warning and it's nothing to worry about. I'm just tryin to figure out how it's still in the build. I cleared the cache, restarted the server, restarted my computer... The console warning is also appearing in my prod app.

[btahir]

I'm still getting this too.

react and react-dom are both on 17.0.2. I'm using next.js (11.0.1--latest), so it could be some build artifact. newSharedArrayBuffer appears twice in the next.js build file, though the one Chrome flags (I assume the first instance) seems to be coming from node_modules/util.

I know it's just a warning and it's nothing to worry about. I'm just tryin to figure out how it's still in the build. I cleared the cache, restarted the server, restarted my computer... The console warning is also appearing in my prod app.

I'm still getting error as well (on React 17.02). Anybody found a workaround?

[agektmr]

Apparently util itself has solved the issue in v0.12.4, but multi-level dependencies are causing this issue. The followings are the libraries that depends on util:

• node-libs-browser@2.2.1
• assert@1.5.0
• assert@2.0.0

I've sent a pull request to fix the issue in assert.