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
no page error, no console output, no term output.
// pages/index.js import dynamic from 'next/dynamic' const TestLoader = dynamic(import('../components/Test'), { ssr: false}) export default () => <TestLoader /> // components/Test.js throw new Error('test') export default () => <div>hello</div>
The text was updated successfully, but these errors were encountered:
seems like an aliasing bug where next/dynamic is getting a copy of react. I haven't tried this yet, will have to in order to see what's going on.
next/dynamic
Sorry, something went wrong.
@developit @onlyfortesting You're better off reporting that to the next team since it doesn't work on the official next template either.
As for why it works on the default import is as the file is executed as a node module before reading the component , thus breaking on the normal.
Changing it to this
const error = ()=>{ throw new Error("test"); } const Test = () => { error(); return <div>hello</div>; }; export default Test;
Gave me the requested error.
Though if you are seeing this happen in a project, please create a similar snippet, would help in debugging
No branches or pull requests
Current Behavior
no page error, no console output, no term output.
Steps to Reproduce (for bugs)
The text was updated successfully, but these errors were encountered: