Getting this error in 'npx frontity dev'

smit.soni22 · 4 July 2019 13:20

SERVER STARTED – Listening @ http://localhost:3000

mode: development
target: module

TypeError: libraries__WEBPACK_IMPORTED_MODULE_2_.Api is not a constructor
at wpSource (webpack-internal:///./node_modules/@frontity/wp-source/src/index.ts:6:925)
at eval (webpack-internal:///./node_modules/@frontity/core/src/utils/merge-packages.ts:7:360)
at Array.forEach ()
at webpack_exports.default (webpack-internal:///./node_modules/@frontity/core/src/utils/merge-packages.ts:7:173)
at webpack_exports.default (webpack-internal:///./node_modules/@frontity/core/src/server/store.ts:5:271)
at eval (webpack-internal:///./node_modules/@frontity/core/src/server/index.tsx:43:68)
at processTicksAndRejections (internal/process/task_queues.js:89:5)
at eval (webpack-internal:///./node_modules/koa-mount/index.js:16:290)

smit.soni22 · 4 July 2019 13:21

smit.soni22 · 4 July 2019 13:36

This error is fixed after replace ‘@ frontity’ package from git.

luisherranz · 4 July 2019 15:06

Could you please indicate the steps to reproduce the problem?

smit.soni22 · 4 July 2019 15:07

yes sure!

npx frontity create my-app && cd my-app
npx frontity dev

that’s it

luisherranz · 4 July 2019 15:10

Could you please do npx frontity info in that folder?

smit.soni22 · 4 July 2019 15:10

ok doing it.

smit.soni22 · 4 July 2019 15:13

Ohh problem is still there after replacing from Git.

Sending npx frontity info in 5 mins

smit.soni22 · 4 July 2019 15:17

npx frontity info

luisherranz · 4 July 2019 15:21

Looking into it. Thanks @smit.soni22.

smit.soni22 · 4 July 2019 15:27

let me know if you need something else or even remote access of my mac.

luisherranz · 4 July 2019 15:30

It looks like it’s not a problem with Frontity itself, but with a dependency that has included a bug. We are trying to find out which one it is.

luisherranz · 4 July 2019 16:35

It’s this bug on the 7.5.0 version of babel which was released 3 hours ago: https://github.com/babel/babel/issues/10162

It looks like they broke the direct exports like this:

export { default as Api } from "./api";

We have changed them to make it work and we are releasing a new version as we speak.

We will change them back once they have fixed the issue.

smit.soni22 · 4 July 2019 16:39

Thanks!

luisherranz · 4 July 2019 16:49

Smit, can you update to wp-source@1.1.6 and let us know if it’s fixed?

smit.soni22 · 4 July 2019 16:51

It’s working after package update!