question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

webpack error --> Plugin name should be specified

See original GitHub issue

🐛 Bug Report

ERROR in ./assets/images/winering-loader.svg
Module build failed (from ./node_modules/@svgr/webpack/dist/index.js):
Error: Plugin name should be specified
    at resolvePluginConfig (/Users/db/winering/core-dev/node_modules/@svgr/plugin-svgo/node_modules/svgo/lib/svgo/config.js:113:13)
    at Array.map (<anonymous>)
    at optimize (/Users/db/winering/core-dev/node_modules/@svgr/plugin-svgo/node_modules/svgo/lib/svgo.js:50:37)
    at Object.optimize (/Users/db/winering/core-dev/node_modules/@svgr/plugin-svgo/node_modules/svgo/lib/svgo-node.js:97:10)
    at svgoPlugin (/Users/db/winering/core-dev/node_modules/@svgr/plugin-svgo/dist/index.js:75:25)
    at run (/Users/db/winering/core-dev/node_modules/@svgr/core/dist/index.js:176:16)
    at Object.transform (/Users/db/winering/core-dev/node_modules/@svgr/core/dist/index.js:182:10)
    at async /Users/db/winering/core-dev/node_modules/@svgr/webpack/dist/index.js:71:18
ModuleBuildError: Module build failed (from ./node_modules/@svgr/webpack/dist/index.js):
Error: Plugin name should be specified
    at resolvePluginConfig (/Users/db/winering/core-dev/node_modules/@svgr/plugin-svgo/node_modules/svgo/lib/svgo/config.js:113:13)
    at Array.map (<anonymous>)
    at optimize (/Users/db/winering/core-dev/node_modules/@svgr/plugin-svgo/node_modules/svgo/lib/svgo.js:50:37)
    at Object.optimize (/Users/db/winering/core-dev/node_modules/@svgr/plugin-svgo/node_modules/svgo/lib/svgo-node.js:97:10)
    at svgoPlugin (/Users/db/winering/core-dev/node_modules/@svgr/plugin-svgo/dist/index.js:75:25)
    at run (/Users/db/winering/core-dev/node_modules/@svgr/core/dist/index.js:176:16)
    at Object.transform (/Users/db/winering/core-dev/node_modules/@svgr/core/dist/index.js:182:10)
    at async /Users/db/winering/core-dev/node_modules/@svgr/webpack/dist/index.js:71:18
    at processResult (/Users/db/winering/core-dev/node_modules/webpack/lib/NormalModule.js:751:19)
    at /Users/db/winering/core-dev/node_modules/webpack/lib/NormalModule.js:853:5
    at /Users/db/winering/core-dev/node_modules/loader-runner/lib/LoaderRunner.js:399:11
    at /Users/db/winering/core-dev/node_modules/loader-runner/lib/LoaderRunner.js:251:18
    at context.callback (/Users/db/winering/core-dev/node_modules/loader-runner/lib/LoaderRunner.js:124:13)
    at __node_internal_ (node:util:281:10)
    at processTicksAndRejections (node:internal/process/task_queues:83:21)
 @ ./src/apps/marketing/pages/Connect.js 10:0-69 257:38-58
 @ ./src/apps/marketing/routes.js 24:0-44 25:19-29
 @ ./src/app/routes.js 12:0-52 16:199-214
 @ ./src/app/index.js 8:0-35 81:66-75

2021-12-02 11:15:00: webpack 5.64.4 compiled with 7 errors in 17877 ms (33c33581ec47412b6d65)

To Reproduce

running the following script: webpack serve --env local --mode=development --config=webpack.config.dev.js

Expected behavior

A clear and concise description of what you expected to happen.

Link to repl or repo (highly encouraged)

Issues without a reproduction link are likely to stall.

Run npx envinfo --system --binaries --npmPackages @svgr/core,@svgr/cli,@svgr/webpack,@svgr/rollup --markdown --clipboard

Paste the results here:

## System:
 - OS: macOS 12.0.1
 - CPU: (16) x64 Intel(R) Core(TM) i9-9980HK CPU @ 2.40GHz
 - Memory: 48.97 MB / 32.00 GB
 - Shell: 5.8 - /bin/zsh
## Binaries:
 - Node: 12.18.3 - ~/.nvm/versions/node/v12.18.3/bin/node
 - Yarn: 1.22.5 - ~/.yarn/bin/yarn
 - npm: 7.20.5 - ~/.nvm/versions/node/v12.18.3/bin/npm
## npmPackages:
 - @svgr/webpack: ^6.1.0 => 6.1.0 

Running Node Version Manager - node -v 16.13.0

package.txt webpack.config.base.js.txt webpack.config.dev.js.txt

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Reactions:3
  • Comments:7 (2 by maintainers)

github_iconTop GitHub Comments

1reaction
dbibbenscommented, Dec 4, 2021

@gregberge just to confirm, this would be the change based on what i read. thanks for the help

svgoConfig: {
  plugins: [
    {
      name: 'cleanupIDs', 
      active: false,
    }
    {
       name: 'prefixIds',
       active: false,
    },
  ],
},
1reaction
gregbergecommented, Dec 4, 2021

Your SVGO config is probably outdated. Please update your SVGO config according to SVGO v2 migrate guide.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Error in Plugin name should be specified · Issue #190 - GitHub
Hey, I'm using Webpack 5 using the Asset Module for images as described in the Asset Management documentation. Now I added the ...
Read more >
Plugin name should be specified' @svgr/webpack svgoConfig ...
The latest SVGO documentation suggests that you need to assign each plugin object a name. Your configuration is out of date so it's...
Read more >
Plugins - webpack
A webpack plugin is a JavaScript object that has an apply method. This apply method is called by the webpack compiler, giving access...
Read more >
tsconfig-paths-webpack-plugin - npm
Using this plugin means that you should no longer need to add alias entries in your webpack.config.js which correspond to the paths entries ......
Read more >
Custom Webpack Config - Next.js
The webpack function is executed twice, once for the server and once for the client. This allows you to distinguish between client and...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found