migrator
migrator copied to clipboard
Tool for migrating stylesheets to new Sass versions
If the entrypoint imports a file that uses variables that were originally defined in the entrypoint, the migrator generates a `@use` that imports the original file. For example: ```scss //...
**Operating System** Windows 10 **Sass Version** 1.55.0 (compiled with dart2js 2.18.1) **Migrator Version** 1.7.1 (compiled with dart2js 2.18.0) After using the migrator on a large number of files, I encountered...
With `@import`, it's possible for a file to refer to a mixin or function that gets redefined later on. Right now `References` will just override the previous definition and treat...
See https://github.com/sass/sass/issues/2831 See specifically https://github.com/sass/sass/blob/main/proposal/color-4-new-spaces.md#deprecated-functions
This mode would allow users to specify a Sass version that they're migrating from, and then the runner would automatically choose to run one or more migrators for breaking changes...
As discussed in https://github.com/sass/sass/issues/2575, there appears to be an issue with `sass-migrator module --verbose --dry-run --migrate-deps` wanting to rename `~` - prefixed imports. Here's a minimum example that hopefully reproduces:...
Right now, if a dependency is migrated in multiple ways by multiple entrypoints, the migrator will error with a message that's not particularly helpful. This should instead display the diff...
See https://github.com/sass/migrator/pull/63#discussion_r295561359 Low priority for now, until more migrators that use `missingDependencies` exist.
Right now something like: ```scss // entrypoint.scss $background: mix(red, blue) @import "library"; // _library.scss $background: green !default; ``` would error, since the patch to add the color namespace and the...