-
Notifications
You must be signed in to change notification settings - Fork 115
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
Plain CSS usage generates pod-styles.css
outside of assets
dir
#47
Comments
If someone wants to pick this up before I can get to it, this should be a simple logic check around the |
It also looks like I don't think I have my head fully wrapped around the intended tree state at various points in the process right now, but it feels like the "with preprocessor" and "without preprocessor" cases are getting a little jumbled together and making it harder to reason about this kind of thing. |
@dfreeman with vanilla CSS, I believe |
In a freshly $ ls -R dist
dist:
assets crossdomain.xml index.html robots.txt testem.js tests
dist/assets:
ember-data.js.map passed.png test-support.css test-support.map vanilla.js vendor.css vendor.map
failed.png test-loader.js test-support.js vanilla.css vanilla.map vendor.js
dist/tests:
index.html c.f. $ ember install ember-component-css && ember build && ls -R dist
# ... snip ...
dist:
app assets crossdomain.xml index.html pod-styles. robots.txt testem.js tests
dist/app:
styles
dist/app/styles:
app.css
dist/assets:
ember-data.js.map failed.png passed.png test-loader.js test-support.css test-support.js test-support.map vanilla.js vanilla.map vendor.css vendor.js vendor.map
dist/tests:
index.html |
Hmm, okay. I tested it as well, by default Ember does add all the CSS files into So it seems like we have two cases: plain CSS should route all files to |
As of now, I confirm that this error is still here. Any updates on fixing? |
you now need to use a postcss import (or equivalent) in order to use with plain css files. The readme has an explanation on how to do this. |
It appears that plain CSS usage generates a
/pod-styles.css
file at the root of the application rather than inside of the/assets
directory.The text was updated successfully, but these errors were encountered: