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

Cannot assign to read only property 'exports' of object '#<Object>' #27

Closed
MiloCasagrande opened this issue Mar 2, 2020 · 1 comment · Fixed by #28
Closed

Cannot assign to read only property 'exports' of object '#<Object>' #27

MiloCasagrande opened this issue Mar 2, 2020 · 1 comment · Fixed by #28

Comments

@MiloCasagrande
Copy link

Version: 4.1.1

Details

After updating to the latest version of @marko/webpack, when I load the app in the browser I get the following error message:

Cannot assign to read only property 'exports' of object '#<Object>'

This prevents the rest of the app to work correctly.

When compiling the project, I also get the following warning:

"export 'default' (imported as 'component') was not found in './index.marko'

repeated multiple times (for each component).

I'm not sure if this is the expected behavior for @marko/webpack 4.1.1, if it's a breaking change compared to the way components are written.

Your Environment

  • Chrome (latest)
  • Firefox (latest)
  • nodejs 12
  • MacOS, Linux

Steps to Reproduce

I tried also with the marko-webpack repository from the markojs examples updating all dependencies to the latest available versions, and I get the same error.

https://github.com/MiloCasagrande/marko-webpack/tree/marko-webpack-4.1.1

@DylanPiercey
Copy link
Contributor

Should be fixed in 4.1.2. Thanks for filing the issue 😄

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

Successfully merging a pull request may close this issue.

2 participants