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

Preloaded scripts warning #2022

Closed
nealalpert opened this issue May 19, 2017 · 7 comments
Closed

Preloaded scripts warning #2022

nealalpert opened this issue May 19, 2017 · 7 comments
Labels
please add a complete reproduction The issue lacks information for further investigation

Comments

@nealalpert
Copy link

We're working on upgrading Next.js from 2.1.1 to 2.3.1 after reading about all the speed optimizations. We're receiving the following warning about the three preloaded scripts that are now included in the head of the page:

screen shot 2017-05-19 at 4 07 10 pm

Did we misconfigure something that's causing these scripts to wait on something else to load?

@arunoda
Copy link
Contributor

arunoda commented May 22, 2017

I haven't seen this before. Tell me a way to reproduce this.
Browser, OS, and app to test.

@arunoda arunoda added the please add a complete reproduction The issue lacks information for further investigation label May 22, 2017
@arunoda
Copy link
Contributor

arunoda commented May 22, 2017

Please re-open once you've them.

@arunoda arunoda closed this as completed May 22, 2017
@khrome83
Copy link
Contributor

@arunoda - This was Chrome 58, on OSX. We are using a custom _document.js but we stopped making a call to <NextScript /> because it was duplicating the insert of the call to the scripts.

We did nothing special to make this happen. It may just be the latest version of Chrome? You may also not having warnings enabled in your console.

<link rel="preload" href="/_next/512eec5c-baf2-4688-b78d-feed85936330/page/" as="script">
<link rel="preload" href="/_next/512eec5c-baf2-4688-b78d-feed85936330/page/_error" as="script">
<link rel="preload" href="/_next/d282b8275bc2041a61eba101ddbbef48/app.js" as="script">

As far as we can tell they are formatted correct.

@arunoda
Copy link
Contributor

arunoda commented May 23, 2017

but we stopped making a call to <NextScript /> because it was duplicating the insert of the call to the scripts.

I didn't get this?

@khrome83
Copy link
Contributor

khrome83 commented Jun 3, 2017

@arunoda - I think we had removed <NextScript> seeing it in viewsource as a duplicate src reference. I was mistaken that we did need it. Because of that we stopped seeing the warning.

@khrome83
Copy link
Contributor

khrome83 commented Jun 3, 2017

@nealalpert - can you close this?

@sojungko
Copy link

sojungko commented Jan 5, 2018

Is there a way to suppress these warnings?

@lock lock bot locked as resolved and limited conversation to collaborators Jan 5, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
please add a complete reproduction The issue lacks information for further investigation
Projects
None yet
Development

No branches or pull requests

4 participants