Skip to content
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 M92, around July 2021. See https://developer.chrome.com/blog/enabling-shared-array-buffer/ for more details. #27059

Closed
mensur-durakovic opened this issue Jul 9, 2021 · 7 comments
Labels
bug Issue was opened via the bug report template.

Comments

@mensur-durakovic
Copy link

mensur-durakovic commented Jul 9, 2021

What version of Next.js are you using?

11.0.1.

What version of Node.js are you using?

14.17.1.

What browser are you using?

Chrome

What operating system are you using?

macOS

How are you deploying your application?

Vercel

Describe the Bug

When you create new NextJS application there is warning is the console:

inpage.js:2 [Deprecation] SharedArrayBuffer will require cross-origin isolation as of M92, around July 2021. See https://developer.chrome.com/blog/enabling-shared-array-buffer/ for more details.

Because of this warning Google Lighthouse report is giving my website lower score in category "Best practices" - Uses deprecated APIs (93/100)

I tried to upgrade to React and React-dom to latest version (17.0.2) but the issue is still here. I have tried everything suggest on SO, nothing helps.

Expected Behavior

I expect no warning messages in the console when I create new NextJS app.

To Reproduce

Create new NextJS app with this command:

npx create-next-app --typescript

run app with command:

npm run dev

Open localhost:3000 and inspect console.

Warning is displayed.

@mensur-durakovic mensur-durakovic added the bug Issue was opened via the bug report template. label Jul 9, 2021
@mattcarlotta
Copy link
Contributor

This is an issue with React/ReactDOM. Make sure you update both to v17.0.2: reference

@mensur-durakovic
Copy link
Author

@mattcarlotta did you read my section "Describe the bug"? My NextJS version is already using 17.0.2 React and React-dom, and it is not resolving the issue.

@mattcarlotta
Copy link
Contributor

mattcarlotta commented Jul 11, 2021

Unable to replicate your issue with your reproduction steps:
Screenshot from 2021-07-11 06-56-58

Screenshot from 2021-07-11 06-54-31

Screenshot from 2021-07-11 06-54-45

Screenshot from 2021-07-11 07-00-35

If you're installing any additional dependencies, please list them.

@mensur-durakovic
Copy link
Author

@mattcarlotta that's very strange. I just repeat all my steps above and I can still see the warning. Only thing that is different is you are using yarn and I am using npm. Also you have higher node version than I have.

Tried with Chrome and Firefox. In Firefox, there is no warning and in Chrome warning is still there:

image

My Chrome version is: 91.0.4472.114 (Official Build) (arm64)

@mattcarlotta
Copy link
Contributor

mattcarlotta commented Jul 11, 2021

I'm running a similar Chrome version: Version 91.0.4472.114 (Official Build) (64-bit), which leads me to believe that npm may be your issue.

Try the following and see if the warning is still present:
A.) Install and run the CRA with Typescript -- I expect this to display the same warning.
B.) Switch to yarn: sudo npm i -g yarn, then yarn create next-app --typescript -- I expect this to possibly fix the issue, but not 100% sure.
C.) Try this workaround -- This shouldn't be required if you're using the newest version of React/ReactDOM. If this works, I suspect that a dependency within your dependency tree is requiring a React version prior to v17.0.2 or a dependency that uses SharedArrayBuffer.

@mensur-durakovic
Copy link
Author

@mattcarlotta I have finally found the reason. I have Chrome extension "Binance Chain" installed on my Chrome. When I disable extension, warning goes away.

Ehh, mistery solved. Thanks for your help!

@balazsorban44
Copy link
Member

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.

@vercel vercel locked as resolved and limited conversation to collaborators Jan 28, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue was opened via the bug report template.
Projects
None yet
Development

No branches or pull requests

3 participants