Migration from legacy NPM package

We are aware of a few breaking changes we made. We are committed to streamline your resource management, thus we tried to make sure your transition is as smooth as possible. If you need assistance during the transition, feel free to get in touch with our tech support at info@respresso.io.

Breaking changes:

• Previously the sass group in the color category contained .scss files. This was fixed. The sass and the scss group contains the corresponding formats. If you want to get the same scss files, you will need to use the scss group instead of the sass in your previous config.

Suggested migration steps:

1. Install the new Respresso CLI on all the machines you want to use to sync resource files.
2. Remove the respresso.json and respresso.lock files that were created by the legacy NPM package.
3. Set up your existing modules with the new CLI. Run respresso init in each module you want to use Respresso. For further instructions, see the CLI's get started page. You should review the synced groups and versions.
4. Run respresso sync for each new respresso.json.
5. Review your imports and file paths. They should not be changed, but if the CLI auto-configured some target overrides, it might place files elsewhere. You can delete any target overrides from the respresso.json config to achieve the same result as with the legacy NPM package.
6. Optionally, set up an NPM script to run sync using npm.