v3.0.1

Fixed

• Support for Meteor 1.6.1
• PostCSS no longer outputs the sourcemap comment, which should fix the "DevTools failed to parse SourceMap" errors in the Chrome console (#104)
• The compiled JS output is now lazy-loaded if located in the imports folder

v3.0.0

[3.0.0] - 2017-11-19

Fixed

• Support for Meteor 1.6 (sort of)

release-1.1.2

• Support for Meteor 1.3.2.4 #24, #28
• Fixed PostCSS source map output (still need to fix paths as they all show up under the root)
• Generated JS is now visible in the client as filename.extension.js (eg, styles.scss.js)
• Generated CSS is now visible in the client as filename.extension.css (eg, styles.scss.css) so they don't overlap with plain CSS files (eg, styles.css) if the user has both in the same directory
• The raw contents of a SCSS file are always used for imports instead of the parsed contents if the file had previously been processed (leading to issues using variables, mixins, etc).
• Stylus error messages updated to say "Stylus" instead of "SCSS"

release-1.1.1

• Stylus support! (thanks @pward123)
• Lazy-loaded files via composition are now actually imported and will be loaded on the client

release-1.0.3

• Caching is disabled as a workaround until proper cache invalidation is implemented.
• CSS modules options in the packages.json file are now reloaded every time the build compiler runs (previously you had to restart Meteor for the changes to take effect). Settings that are used during build plugin registration - such as extensions and specificArchitecture - still require server restarts to take effect.

v1.0.2

Fixed issue #13, where server-side rendering failed when importing lazy-loaded stylesheets