Releases: Debens/gatsby-plugin-scss-typescript
Releases · Debens/gatsby-plugin-scss-typescript
v4.0.13
v4.0.8
v4.0.7
v4.0.3
This release has no feature changes, it was designed around building a better development process.
Adding:
- Commit linting: Using conventional commits to allow for better change tracking
- Adds some snapshot tests. Not the cleanest, but there needs to be something here!
- Adds automatic release management (versioning/tagging) to the pipeline
- Runs test with coverage on push and in the pipeline
- Switches the using eslint w/ tslint
From now on change logs should be generated at: https://github.com/Debens/gatsby-plugin-scss-typescript/blob/master/CHANGELOG.md
v4.0.0
CHANGES:
- b92009a Moved to using Gatsby webpack rules sets for css loading, over building rules as custom. This should allow for the plugin to live alongside Gatsby with fewer changes, and also alongside multiple version of Gatsby at the same time with better support.
- Added
cssExtractOptionsfor mini-css-extract-plugin support - Added minify css plugin
BREAKING CHANGES:
- node-sass has been moved into its own peer dependancy, hence you will need to install it along side the plugin
- Removed
postCssLoaderOptionsandstyleLoaderOptions. Now we are using pre-built rule sets we need to use the pre-build options that come with, see Gatsby webpack utils for how these are built. Most of the options are still supported, just throughcssLoaderOptionsorcssExtractOptions, or you can still extend Gatsby webpack yourself for most bespoke features.
V3.1.0
v3.0.0
Removing the loader dependencies, instead uses the given loaders from Gatsby.
Uses given Gatsby loader and plugin for proper css splitting.
BREAKING CHANGES:
- cssLoaderOptions moves into their own option block to accommodate the new option blocks
stylePluginOptions&styleLoaderOptions
WARNINGS:
- Gatsby's default method for loading the styles generated changes for
buildvsdevelop, hence styles may end up being imported in different orders in production vs development.