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

Build issue #4

Open
MartinN3 opened this issue Dec 3, 2021 · 3 comments
Open

Build issue #4

MartinN3 opened this issue Dec 3, 2021 · 3 comments

Comments

@MartinN3
Copy link

MartinN3 commented Dec 3, 2021

if (child.props?.httpEquiv !== undefined) {

Hello this line with coalescent operator might prevent building project, could we make it more backward compatible by removing it?

@guydumais
Copy link
Owner

Hi @MartinN3,

thanks for your feedback.

Could you give me more details about BACKWARD COMPATIBLE please? Do you mean about ES backward compatibility? If so, can you give a concrete example that prevent building project.

Thanks!

@MartinN3
Copy link
Author

I had probably meant optional chaining.

What i meant to articulate, when i posted issue (it's long time ago) - My nextjs project wouln´t build, i think problem could had been, that optional chaining was introduced in Node v14.

@harperaa
Copy link

harperaa commented Sep 13, 2022

I am seeing same issue, followed your blog exactly, step by step, and got this build error on yarn dev.
TypeError: Cannot add property content, object is not extensible
at[redacted]/node_modules/next-strict-csp/dist/cjs/index.js:60:45
at [redacted]/node_modules/react/cjs/react.development.js:1104:17
at [redacted]/node_modules/react/cjs/react.development.js:1067:17
at mapIntoArray ([redacted]/node_modules/react/cjs/react.development.js:964:23)
at mapIntoArray ([redacted]/node_modules/react/cjs/react.development.js:1004:23)
at mapChildren ([redacted]/node_modules/react/cjs/react.development.js:1066:3)
at Object.forEachChildren [as forEach] ([redacted]/node_modules/react/cjs/react.development.js:1103:
... and so on...

@guydumais could you try a recent fresh build with fresh install of next.js and libraries and see if you get different?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants