You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I can’t see any console.log placed on my component methods after upgrading to 2.3.1 when using npm run dev.
We’re using a custom _document.js and previously included <NextScript />.
We removed <NextScript /> because we noticed it was duplicating the inclusion of Next scripts (e.g. app.js) on the page. After removing it I can’t do console.log on client side when running in development mode.
The text was updated successfully, but these errors were encountered:
I work with @mannyreds11 - Remove <NextScript /> does more than just impact console.log(), it also does not run any code that was present in our page or app.js files. In other words, we really need it.
Looking at view source, we do see two sets of tags though. One set in the head that is added without having <NextScript />, other other set is in the body before the close body tag because that is where <NextScript /> is used.
I can’t see any console.log placed on my component methods after upgrading to 2.3.1 when using npm run dev.
We’re using a custom
_document.js
and previously included<NextScript />
.We removed
<NextScript />
because we noticed it was duplicating the inclusion of Next scripts (e.g. app.js) on the page. After removing it I can’t do console.log on client side when running in development mode.The text was updated successfully, but these errors were encountered: