-
Notifications
You must be signed in to change notification settings - Fork 49
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
Invalid imports from virtual modules halt the build with an unhelpful error #59
Comments
Interesting. For virtual modules, The test suite includes coverage for addons with virtual imports*, so at least in the general case they should be working. Would you be able to share a sample repo that reproduces the issue? *See these files for the test:
|
@dfreeman OK, let me try to talk to my boss first 😹 |
@dfreeman Here it is: https://github.com/choice-form/ember-choice-ui 0.5.x in master branch which works well thanks for your time |
@nightire Thanks for the reproduction! That led me right to the issue. It looks like you have a typo ( In the short term just fixing the typo should let you work around the issue, and I'll try to get a fix out in ember-css-modules in the next couple days so no one else hits this problem. Sorry that you ran into this! |
@dfreeman nice catch, how can I event miss that 🤔, thank you! |
@nightire I'm going to keep this open for now to track fixing the underlying issue, if that's ok with you :) |
* master: Update ember-test-helpers to get rid of the _lookupFactory deprecation Skip --skip-cleanup in tests Released v0.6.5 Update CHANGELOG. Upgrade dependencies Support Ember CLI 2.12 Remove readOnly modifier from `styles` properties Bump dependencies Yarn Fix salsify#59.
In one of our addon's index.js:
and in one of .css file:
This works on ember-css-modules v0.5.x, but after I upgrade to v0.6.2, resolve this import from virtualModules will throw an error:
I was tracking this deeper and found in error has been thrown at https://github.com/salsify/ember-css-modules/blob/master/lib/resolve-path.js#L41 because
addonName
could not be parsed correctly:The text was updated successfully, but these errors were encountered: