Issue on React App deployment

[Sanyaorg]

Error: postcss-svgo: TypeError: Cannot set property 'multipassCount' of undefined

[larsonjj]

Having the same issue. Looks like v1.3.1 is breaking builds.
More debug info: /node_modules/svgo/lib/svgo.js:41:37
CC @GreLI ^

[Sanyaorg]

Temp fix: Just rollback to "svgo": "1.3.0" (add to package.json file)

[GrimzEcho]

Same -- here is the dependency graph with create-react-app

`-- [email protected]
  +-- @svgr/[email protected]
  | `-- @svgr/[email protected]
  |   `-- [email protected]
  `-- [email protected]
    `-- [email protected]
      `-- [email protected]
        `-- [email protected]
          `-- [email protected] deduped

It seems like the break is from 1.3.0 --> 1.3.1, but until this is fixed either on svgo's side or with a Webpack dependency update, the easiest fix is to add a hard requirement to package.json

"dependencies":
   "svgo" : "1.3.0"

then npm install

[asherstoppard]

Issue's stemming from

svgo/lib/svgo.js

Line 41 in 58232a3

info.multipassCount = counter;

Adding info = {} sticky plaster seems to solve the error.

[montydhanjal]

Issue's stemming from

svgo/lib/svgo.js

Line 41 in 58232a3

info.multipassCount = counter;

Adding info = {} sticky plaster seems to solve the error.

// info.multipassCount = counter; info = {}

This fix does resolve my issue but I am using this as a build-in Create React App feature. As soon as i yarn install, this issue will come back. It's a temporary fix.

[GrimzEcho]

Issue's stemming from

svgo/lib/svgo.js

Line 41 in 58232a3

info.multipassCount = counter;

Adding info = {} sticky plaster seems to solve the error.

// info.multipassCount = counter; info = {}

This fix does resolve my issue but I am using this as a build-in Create React App feature. As soon as i yarn install, this issue will come back. It's a temporary fix.

you need to pin a specific version ... try

yarn remove svgo
yarn add [email protected]

or just manually edit your yarn.lock or package.json file

[johndevedu]

Can anyone confirm that this fix works? Tried @BrianHVB 's solution

yarn remove svgo
yarn add [email protected]

But still getting same error.

Edit: See comment below for solution if using yarn. It works!

[dshanley]

@johndevedu I'm still getting the issue -- even with pegging the version to 1.3.0. Looking in node_modules/svgo.js where multipass is referenced, I don't see how this is still generating the error.

[kykint]

Same problem while using gulp-svgmin

[johndevedu]

Yeah @dshanley looking at the commit for 1.3.0, all that's changed is the README.md and other package dependencies. Thanks for confirming.

[kykint]

But with 1.3.0 everything is fine

[fmolina24]

For people using yarn add this to your package.json
"resolutions": { "svgo": "1.3.0" }

[montydhanjal]

For people using yarn add this to your package.json
"resolutions": { "svgo": "1.3.0" }

This resolved my issue. Using CRA. Thanks

[ievgenk]

Had to do this with eslint not too long ago. The solution above works thanks!

[frolad]

react-svg-loader package is also affected, temporary adding "svgo": "1.30" to the package.json works fine

[sidharthachatterjee]

Also seeing this over at https://github.com/gatsbyjs/gatsby

[rafaeldsousa]

For people using yarn add this to your package.json
"resolutions": { "svgo": "1.3.0" }

Not using yarn, but worked fine with npm
https://github.com/rogeriochaves/npm-force-resolutions

[msurguy]

Seeing this error in Vue / Nuxt.js deployments as well due to CSSNano package using SVGO

[aaronblondeau]

To get nuxt builds to work I used the "resolutions" fix from above. However, instead of using a global version of nuxt, I had to add nuxt as a dependency and run it via yarn so that it too would follow the resolutions and use the older version of svgo

yarn nuxt build

[Cherry]

I've submitted a PR at #1176 which resolves this issue.
Until this is merged and released, as others have said, simply pin svgo to 1.3.0 or earlier.

[isjavierdiaz]

Seeing this at NextJS too.

For people using yarn add this to your package.json
"resolutions": { "svgo": "1.3.0" }

This solved the issue though.

[hhphuc12]

remove svgo and reinstall [email protected] not solved my problem

[fengerzh]

"resolutions": { "svgo": "1.3.0" }

Add this line in package.json, then rm -rf node_modules, rm -rf yarn.lock, then yarn to reinstall everything.

[gengengengengen]

"resolutions": { "svgo": "1.3.0" }

Add this line in package.json, then rm -rf node_modules, rm -rf yarn.lock, then yarn to reinstall everything.

I am using gatsby and met this problem.
The version of "svgo" is 1.3.0 and works well in my local environment but can't build when deploy to remote server (Cloud Foundry).

[johnnymillergh]

Now not only this error happens during React deployment but also happens during Vue deployment. Same error message. This is how I solved this issue.

1. Add [email protected] in dependencies, package.json

   "dependencies": {
     ...
     "svgo": "1.3.0"
   },

2. Add following statement in package.json

   "resolutions": {
     "svgo": "1.3.0"
   }

3. Done.

Hope this will help you guys who facing this issue as well. 😁

[namcancode]

"resolutions": { "svgo": "1.3.0" }
done

[Gastonite]

[rakibtg]

[abdennour]

Oops! What's a nightmare you did guys 😭
But fixed...😄!
I am DevOps release engineer designing CI/CD of a lot projects.
This means I have the responsibility to fix all pipelines, namely frontend apps pipelines....
Happy it works and thanks for the author of this #1174 (comment) comment

[SecondeJK]

For Nuxt 2:
pushing svgo down to 1.3.0 via resolutions doesn't result in a build.

Now getting:
Error: Cannot find module 'css-tree'
instead.

[jantimon]

@SecondeJK you don't have to revert svgo to 1.3.0 anymore - your error is probably unrelated

[SecondeJK]

@jantimon thanks - realised it's because I last pulled node modules when it was still a problem. Deleted lock, reinstalled, Nuxt happy with building.