Closed st-h closed 1 year ago
SAMPLE_FEATURE_FLAG is not actually defined in this repo. Not sure if it is ember possibly embroider/macros.
This could be an issue with many addons being on different versions of embroider/macros. In my own application I have the following trying to fix this. Curious if you try something like this and update to a later (or latest) version if that might help. I used this to fix ember-cli-babel as well. Since ember-cli-mirage specifies a version of mirage, this also lets me use the higher version of mirage without waiting for ember-cli-mirage to update.
"resolutions": {
"miragejs": "~0.1.46",
"@embroider/macros": "^1.9.0",
"@embroider/util": "^1.9.0",
"ember-cli-babel": "^7.26.1",
"@fortawesome/fontawesome-svg-core": "1.2.35"
}
I also ended up pinning @embroider/macros to 1.9.0 and the error went away.
Great, This is really an issue all addons have (since so many depend on embroider/macros) and keeping up to date yet supporting older versions
Per https://github.com/embroider-build/embroider/issues/1077#issuecomment-1016689755:
In the case of @embroider/macros it is safe to replace all of 0.x with ^1.0.0.
Is there a current fix for this or workaround for this?
i've tried pinning the resolutions like the above suggestions.. but it has not worked .. i'm stuck at ember 4.8 and data 4.7 😢
I currently am on ember data 4.11.3 with the following pins. Had to add ember modifier to them until all the addons Im using get updated to 4.0
"resolutions": {
"miragejs": "~0.1.47",
"@embroider/macros": "^1.10.0",
"@embroider/util": "^1.10.0",
"ember-cli-babel": "^7.26.1",
"ember-modifier": "^3.2.7",
"@fortawesome/fontawesome-svg-core": "1.2.35"
}
eh.. seems like any resolution i try to pin i get the exact same error.. time to dig through some logs.. thanks though
@grapho Not sure if this is helpful, but it wasn't working for me either. Turns out "resolutions" is yarn specific, and if you're using npm you have to use "overrides" instead.
Thats a shame that npm does not use the same section name. Any idea if pnpm has the capability and what word they use?
Looks like pnpm has pnpm.overrides
Had same error, using ember-cli-mirage@v3.0.0-alpha.3
fixed it
@st-h anything else actionable here or should we close this?
Please feel free to close. Sorry, but I no longer use mirage.
For clarification, do you no longer use mirage? or use mirage just not this addon? If you no longer use mirage, what have you replaced it with?
As an FYI I still use mirage, but no longer use this addon.
If anyone still looking for a solution - try locking @embroider/macros and @embroider/utils to v1.10.0
together with setting the flag SAMPLE_FEATURE_FLAG
to false
as described on the following page Package @ember-data/canary-features.
Tested with ember-data v4.8.4
and v4.12.5
and together with ember-cli-mirage v2.4.0
.
I upgraded ember-data from 4.7 to 4.8.0. When building the app, I see the following build error, which traces back to ember-cli-mirage. Downgrading ember-data to 4.7.0 fixes the issue.