@nathantreid, I have just installed your module with sugarss support… Well, now I pray for you! I have sugarss set to be as much similar to stylus as possible, so now I can say that I can easily use modular stylus w/o stylus itself. It works great!
After many build failures, I gave up on 1.3.0, and I just now released 2.0.2. As of 2.0.0, the node-sass, stylus, and sugarss npm packages are no longer bundled with the app, allowing the user to only install the ones they need via meteor npm install.
It also means I don’t have to use the Meteor build servers anymore, so publishing only takes 1 command and 30 seconds.
Finally got it! v2.1.0 includes support for .css files.
I was supposed to enjoy some light reading tonight before bed but instead my brain got caught on the .css issue and wouldn’t let go until I finished (that was about 4 hours ago, oops…). Anyway, I dug into the build plugin system again and this time it clicked.
Just replied on the issue, but I’ll repost it here as well so others can see it:
Given the error message:
While processing files with nathantreid:css-modules (for target
So the issue with my project was that setting the specificArchitecture option with either “os” or false was causing scss import issues. I’ve reported the issue under the main repo here, waiting to hear back. Hopefully this provides a temporary solution for others.
Yeap, I just removed specificArchitecture from package.json entirely. So that means the server side of things right now, and it seems like Nathan is working on the issue. I referenced the open issue in my previous message above if you want to take a look.