TypeError: acorn__WEBPACK_IMPORTED_MODULE_2__.Parser.extend is not a function

[davixyz]

I'm coming from this repo: https://github.com/pedronauck/docz
Which has a dependency tree like this

└─┬ [email protected]
  └─┬ [email protected]
    └── [email protected]  deduped

Seems that [email protected] introduced an issue with this:
TypeError: acorn__WEBPACK_IMPORTED_MODULE_2__.Parser.extend is not a function

If we lock to [email protected] everything works again. Any insight?

[adrianheine]

Thanks for the report! Can you link to a small example reproducing this issue? I tried the basic example from docz, but couldn't get it to work at all for me.

[davixyz]

Hi @adrianheine
Here's the repo with the issue:
https://github.com/davixyz/docz-issue

Basically seems that theme-default is depending on react-live, which is depending on buble and latest version is breaking. Seems to work again when I lock [email protected]

[adrianheine]

Thanks, I can reproduce the issue by cloning your repo, running npm i && npm run dev and then opening the served page in my browser. I'll have a look.

[adrianheine]

Hm, acorn__WEBPACK_IMPORTED_MODULE_2__ is [email protected], but bublé depends on acorn@6. Apparently, npm did set up the dependencies correctly, since echo "const x = 1" | node_modules/.bin/buble works (I can see an [email protected] in node_modules/buble/node_modules, too). So, on the server-side, everything seems to be correctly set-up, but somehow webpack bundles bublé with the wrong acorn version.

It's obvious that [email protected] doesn't have this issue since I temporarily bundled acorn in the bublé package in that version. [email protected] also depends on an external acorn@6, so that doesn't work either, and [email protected] uses the old acorn@5, so that works with the acorn version webpack bundles it with.

I suggest to open corresponding issues with webpack (since it is doing the wrong bundling) and react-live (since it is the package depending on bublé). Further, it makes sense to update all dependencies on acorn@5, since that's a safe way to fix this issue for you and also a good thing to do for everyone. Currently, [email protected] (via [email protected] via [email protected]) and [email protected] (this can be solved by upgrading to [email protected]) pull in acorn@5.

[davixyz]

If the issue is not here, we can close this.