-
-
Notifications
You must be signed in to change notification settings - Fork 107
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
"export 'default' (imported as 'stringify') was not found in 'fast-json-stable-stringify' #399
Comments
Same problem here, migrating from 2.3.0 to 3.2.1 |
Did you try to delete the node_modules folder and do a fresh install? |
Yep, no dice. FWIW, my app was bootstrapped with vue-cli 4.0.5.
|
And did you add the transpileDependencies option in the vue.config.js file? |
Yep: // vue.config.js
module.exports = {
lintOnSave: false,
transpileDependencies: ['feathers-vuex'],
chainWebpack: config => {
config.module
.rule("vue")
.use("vue-svg-inline-loader")
.loader("vue-svg-inline-loader")
.options({ /* ... */ });
}
} |
I was able to fix this locally with yarn add babel-plugin-transform-commonjs-es2015-modules --dev // babel.config.js
module.exports = {
plugins: ['transform-commonjs-es2015-modules'],
presets: [
'@vue/cli-plugin-babel/preset'
]
} No idea why this suddenly broke, though... From what I can gather, when babel tries to transpile feathers-vuex, it chokes on the |
Hey @markneub , Do I have to add babel.config.js to another file (eg nuxt.config.js) to make it work or is it working for you just as explained above?
KR |
Hey @klaus1978, all I had to do to get my setup working is what I explained above. Since you're using Nuxt I expect it will be a little different. From the Nuxt docs on modifying your babel configuration, it looks like you could maybe try adding something like the following: // nuxt.config.js
module.exports = {
// (maybe some existing config here)
build: {
babel: {
plugins: ['transform-commonjs-es2015-modules']
}
}
} |
Hey @markneub , Thanks a lot |
Thanks for reporting, @klaus1978 and @markneub . I haven't run into this issue, yet. I'll leave this open for a while before I either update the docs or find another solution that doesn't require a workaround. |
not work with i18n-nuxt
|
It's a pretty light-weight module, so maybe the best solution would be to bring the That would make it so we don't have to do the babel workaround. |
Hey @marshallswain , |
I'm having a similar problem with 'sift':
I fixed with: // nuxt.config.js
module.exports = {
// (maybe some existing config here)
build: {
babel: {
sourceType: 'unambiguous'
}
}
} |
This issue need some love. |
I'm still not sure how to reproduce this issue. Does anybody have a repo they can share? |
Please, if you can, comment there! epoberezkin/fast-json-stable-stringify#10 Maybe seeing more interested people we can reach a solution soon. |
Hi!
I'm getting:
|
@inghuguesboni did you fix
|
after update to last version problem has fixed !
|
Just for information, my solution (it might not be appropriate for you) is to set
in package.json. |
Yes I have it. Here is my quasar.conf.js / build:
|
Update your file like this to fix this problem
|
I've added a section in the docs to both the Getting Started page and the Nuxt page that links to this issue as a reference for those who have build issues. I still have yet to run into this issue, at all. Since this isn't something that can be resolved in a satisfactory manner inside feathers-vuex, I'm closing the issue. https://vuex.feathersjs.com/nuxt.html#resolving-build-issues |
Ok had the same problem on existing project upgraded from quasar 1.6 to 1.9 latest then tried feathers-vuex 2.31 to 3.9 latest. tried the babel no luck. node v.12 deleted yarn.lock and node_modules with fresh yarn did the trick. all good now. |
Hi,
After updating from v2.3.1 to v3.2.1 I now get the error message:
"export 'default' (imported as 'stringify') was not found in 'fast-json-stable-stringify'
index.js?a08a:3 Uncaught TypeError: Cannot assign to read only property 'exports' of object '#'
at Module.eval (index.js?a08a:3)
at eval (index.js:84)
at Module../node_modules/feathers-vuex/node_modules/fast-json-stable-stringify/index.js (vendors.app.js:4344)
at webpack_require (runtime.js:791)
at fn (runtime.js:151)
at Module.eval (utils.js:69)
at eval (utils.js:537)
at Module../node_modules/feathers-vuex/dist/utils.js (vendors.app.js:4320)
at webpack_require (runtime.js:791)
at fn (runtime.js:151)
Going back to a version <3.xx seems to solve the issue again
KR Klaus
The text was updated successfully, but these errors were encountered: