Apostrophe 3.21.1: hotfix for backwards compatibility issue with sass

[boutell]

Yesterday, sass version 1.50.2 was released. This version reports an error when building Apostrophe's admin UI styles, preventing Apostrophe projects from starting up successfully.

Today we've released apostrophe version 3.21.1, which temporarily pins our dependency on sass to 1.50.1, allowing builds to succeed. In the coming sprint we'll analyze whether the error with sass 1.50.2 is due to an error in our styles, a bug in sass, or a backwards compatibility break in sass, and take appropriate next steps. For now we've done the simplest possible thing to ensure your projects work smoothly.

If you are seeing this error:

SassError: RangeError: Invalid value: Not in inclusive range 0..145: -1

You can fix it with this command:

npm update

In a development environment, you might need to also run this command:

node app @apostrophecms/asset:clear-cache

Thanks for reading.

[RajanTpss]

Hello @boutell , I am still facing same as above error even after running the commands.

Please guide me, what else we need to do to remove this error.

Thanks

[boutell]

You must "npm update" your project.

If that does not work, check "package.json" and make sure the version number of the dependency on "apostrophe" starts with a "^" and is not locked down (no "^").

[RajanTpss]

@boutell , Above is worked for me. Initially this error was comming while we making the build in terminal. Now error is in the browser but build process at console/terminal is successfull. Please have a look at the screenshots :

Initial Error while making build in console

After npm update and remove "^" this from package.json file. Buld in console was working successfully.

But now the error is in browser console as shown in above screenshot.

Screenshot "package.json" file.

Please guide me to resolve this error.

Thanks

[boutell]

Note that "npm update" and "npm install" are not the same.

[boutell]

The "^" is a good thing. You need it.

Without it you are forever locked on apostrophe 3.5.0, which was released several months ago. We have made many fixes since then. Please add the "^" back in front of that and do "npm update".