You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When an embroider app using ember-css-modules depends on a v1 / classic addon using ember-css-modules, the generated scoped classnames in the css file don't match the classnames injected in the templates.
The text was updated successfully, but these errors were encountered:
wondersloth
changed the title
Doesn't have correct path when generating-scoped-name during an embroider build.
css file hash doesn't use correct path when generating-scoped-name during; when an embroider app build is consuming an addon using ecm
Apr 15, 2022
wondersloth
changed the title
css file hash doesn't use correct path when generating-scoped-name during; when an embroider app build is consuming an addon using ecm
css file hash doesn't use correct path when generating-scoped-name in embroider app build, when consuming an addon using ecm
Apr 18, 2022
wondersloth
pushed a commit
to wondersloth/ember-css-modules
that referenced
this issue
May 11, 2022
Problem
When an embroider app using
ember-css-modules
depends on av1
/ classic addon usingember-css-modules
, the generated scoped classnames in the css file don't match the classnames injected in the templates.Example of Bug
https://github.com/wondersloth/embroider-x-ember-css-modules
Investigation
generate-scoped-name
the paths used lack themoduleName
and only contains the relative path in the module.Classic (Working)
Steps to Reproduce
OUTPUT
Embroider (Broken)
Steps to Reproduce
OUTPUT
Output from
ember-css-modules
Differences
In an embroider build the file paths don't contain the the
modulePrefix
between classic vs embroider:vendor.css
GOOD
BAD
The text was updated successfully, but these errors were encountered: