New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Deprecation] SharedArrayBuffer will require cross-origin isolation as of M91, around May 2021 #21708
Comments
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
I'm not entirely sure how next.js works, but since it has dependency with React, this issue might be related: facebook/react#20829 |
Yep this is coming from React and has already been fixed (as linked above). |
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 |
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. |
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. |
Chrome 92 started to disable `SharedArrayBuffer` without cross-origin isolation which can be enabled by [sending the page with special HTTP headers](https://web.dev/cross-origin-isolation-guide/). This change causes Chrome to emit a warning in DevTools console and [developers are confused with the message](vercel/next.js#21708). `util` is one of the libraries that uses `SharedArrayBuffer` and is causing the warning to appear in the console. Luckily, the issue in `util` has been resolved in v0.12.4 and I would like to propose applying the fixed version to this library.
Apparently
I've sent a pull request to fix the issue in |
Chrome 92 started to disable `SharedArrayBuffer` without cross-origin isolation which can be enabled by sending [the page with special HTTP headers](https://web.dev/cross-origin-isolation-guide/). This change causes Chrome to emit a warning in DevTools console and [developers are confused with the message](vercel#21708). `util` is one of the libraries that uses `SharedArrayBuffer` and is causing the warning to appear in the console. Luckily, the issue in `util` has been resolved in [v0.12.4] and I would like to propose applying the fixed version to this library. For fixing vercel#21708
Chrome 92 started to disable `SharedArrayBuffer` without cross-origin isolation which can be enabled by sending [the page with special HTTP headers](https://web.dev/cross-origin-isolation-guide/). This change causes Chrome to emit a warning in DevTools console and [developers are confused with the message](#21708). `util` is one of the libraries that uses `SharedArrayBuffer` and is causing the warning to appear in the console. Luckily, the issue in `util` has been resolved in [v0.12.4] and I would like to propose applying the fixed version to this library. For fixing #21708 ## Bug - [x] Related issues linked using `fixes #number` - [ ] Integration tests added - [ ] Errors have helpful link attached, see `contributing.md` ## Feature - [ ] Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added - [ ] Documentation added - [ ] Telemetry added. In case of a feature if it's used or not. - [ ] Errors have helpful link attached, see `contributing.md` ## Documentation / Examples - [ ] Make sure the linting passes
This issue has been automatically locked due to no recent activity. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you. |
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:
Expected Behavior
No warnings in the console
To Reproduce
Run
npm run dev
ornpx next dev
in the terminal in a Next.js project.The text was updated successfully, but these errors were encountered: