Stylus Asset Support #386
Merged
Stylus Asset Support #386
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This was referenced Jul 9, 2020
This was referenced Aug 16, 2020
This was referenced Aug 27, 2020
This was referenced Mar 23, 2021
This was referenced May 31, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request adds stylus support to sails and introduces a minor refactoring of the css assets code which should make it easier to add other css languages (although they are still hardcoded into assets/index.js.. that should probably change at some point).
I realize there is a discussion going on in #240 about how best to integrate with yeoman. As a sails newb I did not want to complicate things by trying to learn two frameworks at once (and yeoman does not generate simple code) so I built this to keep things simple and sails-centric.
Cheers,
Rob
Originally #371