We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Followed through @jherr 's video
Called my consumer nextjs app next-app-2.
next-app-2
After following instructions and running the consumer app I got a blank screen.
fiddled around with _document.js and next.config.js - commenting out stuff here and there which got it working.
_document.js
next.config.js
re-added execution of MergeRuntime in config file and recreated blank screen.
MergeRuntime
Opened source files and main.js... next.js static chunk and saw that the eval got broken by the next-app-2 name:
main.js...
eval
Changing the name in the config file to a camelCase fixed the issue.
Could be good to add protection from this, or add documentation not to use that sort of app name (at least in the next.config.js)
The text was updated successfully, but these errors were encountered:
not a valid variable... works as expected. You can set library type to window, instead of the default var which should make it work with dashed vars
var
Sorry, something went wrong.
No branches or pull requests
Followed through @jherr 's video
Called my consumer nextjs app
next-app-2.After following instructions and running the consumer app I got a blank screen.
fiddled around with
_document.jsandnext.config.js- commenting out stuff here and there which got it working.re-added execution of
MergeRuntimein config file and recreated blank screen.Opened source files and
main.js...next.js static chunk and saw that theevalgot broken by thenext-app-2name:Changing the name in the config file to a camelCase fixed the issue.
Could be good to add protection from this, or add documentation not to use that sort of app name (at least in the next.config.js)
The text was updated successfully, but these errors were encountered: