This is probably not a problem with postcss-easy-import itself, but I wanted to get your insights, so here goes:
I'm using postcss-easy-import to import css files from the node_module folder, which used to work flawlessly.
After updating our project to the latest version of Ember cli (3.7) things stopped working. I think might be related to Ember cli > 3.5 upgrading to broccoli 2 which uses the system temporary folder when building. PostCSS now throws a warning with the message that it can't find the files that are stored in the node_modules folder.
The weird thing is that if I use postcss-import directly the files are found. So while the problem is probably caused by broccoli, I still think that something can be done in the postcss-easy-import module resolver.
Any idea what resolve-module.js is doing differently than postcss-import's to make it not find the files?
This is probably not a problem with postcss-easy-import itself, but I wanted to get your insights, so here goes:
I'm using postcss-easy-import to import css files from the node_module folder, which used to work flawlessly.
After updating our project to the latest version of Ember cli (3.7) things stopped working. I think might be related to Ember cli > 3.5 upgrading to broccoli 2 which uses the system temporary folder when building. PostCSS now throws a warning with the message that it can't find the files that are stored in the node_modules folder.
The weird thing is that if I use postcss-import directly the files are found. So while the problem is probably caused by broccoli, I still think that something can be done in the postcss-easy-import module resolver.
Any idea what
resolve-module.jsis doing differently than postcss-import's to make it not find the files?More technical details: I'm using an addon called ember-cli-postcss which uses broccoli-postcss-single under the hood.