@embroider/macros' dependencySatisfies does not understand canary versions
See original GitHub issuerelated to: https://github.com/embroider-build/embroider/issues/1057
version is: DEBUG: Ember : 4.2.0-alpha.1.canary+ef2ad15f
my hunch is that the existing comparison code isn’t expecting this many specifiers after alpha.1
Issue Analytics
- State:
- Created 2 years ago
- Comments:28 (6 by maintainers)
Top Results From Across the Web
[Embroider] dependencySatisfies gives wrong answer for ...
Hey, I have a similar problem to Help needed - struggling to find/resolve a deprecation : I'm trying to get rid of the...
Read more >@embroider/macros | Yarn - Package Manager
@embroider/macros. A standardized solution for modifying your package's Javascript and Glimmer templates at app-compilation-time.
Read more >@embroider/macros - npm
Start using @embroider/macros in your project by running `npm i @embroider/macros`. ... or false if the dependency was not satisfied.
Read more >ember-auto-import - UNPKG
12, - ENHANCEMENT support v2 addons that contain @embroider/macros ... relax semver check to tolerate shared versions that satisfy all consumers.
Read more >embroider-build - Bountysource
Traditionally, ember addons each bring their own entirely separate babel that only processes their own code. Likewise, the app has its own independent...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I’m on
4.1.0
. No idea if that matters. I’m doing only basic stuff what a kid can do, so no complexity of an experienced developer (I’m more a Python guy). I also don’t haveresolutions
in mypackages.json
and I have only the render-modifier inside thedependencies
. Is it possible that is has something to do with caching?But now you are on your own again 🥲
idk what craziness my app’s addons are causing, but I’ve had to add these
resolutions
in my root package.json:my surface issue remains though – so now I need to figure out why
version
is undefined –@ember/render-modifiers
lack of peerDependencies seems to not matter (now that I’m using the correct version of@embroider/util
, all ember-source resolves are found, but have undefined version)