-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Imported DEPRECATE_REFERENCE_INTERNAL_MODEL from @ember-data/private-build-infra/deprecations which is not a supported flag. #7221
Comments
+1 |
I think this may be related to the node version. I have no problem building in production, where we have 12.18.0. However the bug report shows node 14.1.0 and I'm seeing the same locally with 14.4.0. |
We use the @rwjblue have you encountered this yet? |
Thank you for your feedbacks. Will be give a solution in future for newer node-versions? |
Tested with nodejs 12.18.1, encountered the problem, removed node_modules, ran npm update, npm install, problem still present, repeated rm, update, install and problem got fixed. Apparently it is intermittent! Maybe it is bound to the load order of modules, dunno... Does it work for you? |
No, I haven't seen this. |
I tried with 10.16.0, 12.18.1, and 14.0.0, but my suite fails with the above error for all. |
Ran in it as well on node v10.15.3. Doing |
@amk221 did you do a fresh install between node versions? If not then your modules would have been whatever the version of npm the first install used gave you. |
Yep, my bad. All fine. |
Hi. I'm having the same issue. I'm running node v12.18.2 and the issue is still there even after a fresh install of node. I don't even use ember-data in my app. |
@Nippius what does yarn why ember-data tell you? |
@Nippius even better: |
@runspired Thanks, here's the output: yarn list v1.21.1 PS: Not sure if relevant but I usually use npm |
Ok I don't understand.. after installing yarn, |
@Nippius thanks! If using npm you can use I'd like the output of |
@Nippius also feel free to hit me up in discord, may make iteration here faster :) |
@runspired Unfortunately I'm on my work PC so I can't install discord :/ I had some free time today so I decided to move to yarn. It's not the first time I've had problems with npm... Here's the output of Anyway it's building fine now when using yarn, so I'll keep using it. |
@Nippius if you aren’t using ember-data then you’ll save yourself a sizeable chunk by removing it from your package.json 😅 was worried another dep was bringing it in for you transitively but that says it’s explicitly specified. |
@runspired ahah fair enough but I'm fairly new to ember (and frontend in general) so I didn't want to mess around with it yet. I've removed it and I'll add it when the time comes :) Thank you once again! |
Solved it by doing Is this an issue with Ember Data? If not, perhaps we can close this issue? |
Hey. It works fine. Thank you!!! |
Encountered the same problem when I was upgrading from 3.18. |
Doesn't appear that this is completely resolved on the 3.20 LTS, ran into this today when upgrading from 3.16. |
@Samsinite its not an issue with ember-data but (Mostly) various bugs with how package managers handle updates and hoisting of dependencies. There’s also a set of cases for which folks have more than one dependency on ember-data in their dependency tree leading to potential conflicts. The best bet if you hit this is to blow away node modules and reinstall, but if that still errors then regenerate the lock file, and if that still errors then check why you have more than one version in your dependency tree and work to resolve that. |
Upgraded a large project from 3.17 to 3.21 and hit this. |
Avoid issues found in #7221 and others
Avoid issues found in #7221 and others
Avoid issues found in #7221 and others
Avoid issues found in #7221 and others
Avoid issues found in #7221 and others
Avoid issues found in #7221 and others
Avoid issues found in #7221 and others
Hi all! The fix in #7329 has been backported to lts/release/main branches. |
Hey there...
Since [email protected] i obtain a failure message when i want to build the app with "ember serve".
I have updated all own addons and updated all packages with npm-check (instead of npm update).
I hope you can help me.
Here is the log from ember builder:
ENV Summary:
TIME: Wed Jun 10 2020 08:45:13 GMT+0200 (Mitteleuropäische Sommerzeit)
TITLE: ember
ARGV:
EXEC_PATH: /usr/local/bin/node
TMPDIR: /tmp
SHELL: /bin/bash
PATH:
PLATFORM: linux x64
FREEMEM: 3315044352
TOTALMEM: 16644083712
UPTIME: 5353
LOADAVG: 1.66162109375,1.068359375,1.37158203125
CPUS:
ENDIANNESS: LE
VERSIONS:
ERROR Summary:
at PluginPass.ImportSpecifier (/var/www/apps/projects/stoma-navi/node_modules/babel-plugin-debug-macros/src/index.js:38:19)
at newFn (/var/www/apps/projects/stoma-navi/node_modules/@babel/traverse/lib/visitors.js:179:21)
at NodePath._call (/var/www/apps/projects/stoma-navi/node_modules/@babel/traverse/lib/path/context.js:55:20)
at NodePath.call (/var/www/apps/projects/stoma-navi/node_modules/@babel/traverse/lib/path/context.js:42:17)
at NodePath.visit (/var/www/apps/projects/stoma-navi/node_modules/@babel/traverse/lib/path/context.js:90:31)
at TraversalContext.visitQueue (/var/www/apps/projects/stoma-navi/node_modules/@babel/traverse/lib/context.js:112:16)
at TraversalContext.visitMultiple (/var/www/apps/projects/stoma-navi/node_modules/@babel/traverse/lib/context.js:79:17)
at TraversalContext.visit (/var/www/apps/projects/stoma-navi/node_modules/@babel/traverse/lib/context.js:138:19)
at Function.traverse.node (/var/www/apps/projects/stoma-navi/node_modules/@babel/traverse/lib/index.js:84:17)
at NodePath.visit (/var/www/apps/projects/stoma-navi/node_modules/@babel/traverse/lib/path/context.js:97:18)
in /tmp/broccoli-476994BR56YQCITg/out-239-funnel
at broccoli-persistent-filter:Babel > [Babel: @ember-data/store] (Babel: @ember-data/store)
in /tmp/broccoli-476994BR56YQCITg/out-239-funnel
at broccoli-persistent-filter:Babel > [Babel: @ember-data/store] (Babel: @ember-data/store)
at PluginPass.ImportSpecifier (/var/www/apps/projects/stoma-navi/node_modules/babel-plugin-debug-macros/src/index.js:38:19)
at newFn (/var/www/apps/projects/stoma-navi/node_modules/@babel/traverse/lib/visitors.js:179:21)
at NodePath._call (/var/www/apps/projects/stoma-navi/node_modules/@babel/traverse/lib/path/context.js:55:20)
at NodePath.call (/var/www/apps/projects/stoma-navi/node_modules/@babel/traverse/lib/path/context.js:42:17)
at NodePath.visit (/var/www/apps/projects/stoma-navi/node_modules/@babel/traverse/lib/path/context.js:90:31)
at TraversalContext.visitQueue (/var/www/apps/projects/stoma-navi/node_modules/@babel/traverse/lib/context.js:112:16)
at TraversalContext.visitMultiple (/var/www/apps/projects/stoma-navi/node_modules/@babel/traverse/lib/context.js:79:17)
at TraversalContext.visit (/var/www/apps/projects/stoma-navi/node_modules/@babel/traverse/lib/context.js:138:19)
at Function.traverse.node (/var/www/apps/projects/stoma-navi/node_modules/@babel/traverse/lib/index.js:84:17)
at NodePath.visit (/var/www/apps/projects/stoma-navi/node_modules/@babel/traverse/lib/path/context.js:97:18)
=================================================================================
The text was updated successfully, but these errors were encountered: