CssMin | Clone of CssMin for http : //packagist.org/about-composer | Build Tool library

Node.js 4.4.4 is absolutely ancient.

It doesn't even show up on this page of releases, which says in part:

After six months, odd-numbered releases (9, 11, etc.) become unsupported, and even-numbered releases (10, 12, etc.) move to Active LTS status and are ready for general use. LTS release status is "long-term support", which typically guarantees that critical bugs will be fixed for a total of 30 months.

Version 4.4 is well beyond its maintenance window, and I strongly urge you to upgrade this project.

Having said that, there's a good chance you can get Heroku to run Node.js 10 to match your local version. Heroku only officially supports the current and active LTS releases, but it doesn't prevent you from using older releases:

Since Heroku is based on a standard Ubuntu Linux stack, you can run most Node versions (>= 0.10.0) on the platform. However, the testing and support focus of the buildpack will be oriented around active LTS and Stable releases.

Update the engines section in your package.json:

You can use commands and do the following:

UPDATE:

Looking at where the error is raised (in django-compressor.compressor.base) we find the following:

I have fixed the issue by myself,after observing the error above(Error: Unsupport format: CSS).The checked my index.html file,that the code like this

I am not entirely sure which of the following was the key to success but here's what I did to resolve this:

1. Delete the node_modules folder from my project, commit and then modify my .gitignore to exclude it from the repository permanently (yes, I know this one is a bit controversial as some people say the folder should be checked in)

2. Update the versions of the dependencies in the package.json file

3. Specify the specific version of NodeJs (and thus npm) to use. I did this by simply adding a step in the Azure build pipeline. Interestingly, the very latest version (15.2.1 at the time of writing this) did not work, however the LTS version 14.15.1 did work.

Some combination of those three changes did resolve the problem for me. I am leaving this information here in case someone else faces this same error message.

The solution I found was to downgrade to NodeJs v11.15.0 and use gulp 3.9.1.

If anyone out there has a better option I'd be keen to hear it.

Finally I found the solution.

So, following the migration from Symfony 2.8 to symfony 3.4, you have to move the bootstrap.php.cache file from the "app" folder to the "var" folder and so, you have to modify the path of this file in the phpunit.xml configuration.

Set the zeroUnits option to false in your cssmin task.

For instance:

Node.js doesn't get bundled with the source code of apps. The package.json might have a section called "engines" in which it will state what version you should be using.

If the root package.json doesn't have the "engines" section, then it may be posable that the some of the dependencies do say which version they require to be used. It would be kind of annoying going through each one to check, so a good way would be just to download a version of Node and run npm install. If everything works, then you know that the Node version the app was created in is most likely older (its a bit tedious, I know).

Another thing you could look for (but might not be to helpful) would be to check when the files of the source code were created (especially the package.json file), and find the Node version that was released around that time. This wont be as accurate as the first method but it will give you a working version of Node.

When it comes down to it though, its probably always best to use the most up to date version (or the most recent LTS version) as they come with all the latest security patches and improvements.