npm run build is resulting in duplicate IDs
See original GitHub issueI’m seeing really odd behavior from the npm run build command lately. After updating nsi-collector data and then running npm run build
I end up with duplicate IDs. The duplicate IDs always seem to be two brand with the same name, but different case. Sometimes it seems like the generic regex should also be removing them. Here’s an example of a failure: https://github.com/osmlab/name-suggestion-index/actions/runs/1595091609
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (2 by maintainers)
Top Results From Across the Web
Getting build error occurred when running npm run build
Open 2nd terminal and execute "npm run build". As the API is running in localhost:3000, it will build properly. Config/index.js const dev = ......
Read more >Duplicate module bundles when optimized dependencies are ...
Describe the bug Duplicate module bundles when optimized dependencies are reloaded during build. It was very hard to reproduce this bug...it ...
Read more >react-helmet - npm
Supports attributes for body , html and title tags. Supports server-side rendering. Nested components override duplicate head changes. Duplicate ...
Read more >Code Splitting - webpack
If there are any duplicated modules between entry chunks they will be included in both bundles. It isn't as flexible and can't be...
Read more >Finding and fixing duplicates in webpack with Inspectpack
Needlessly duplicated dependencies produce larger, ... Let's begin with a common frontend build situation wherein npm (or yarn ) "get" code ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I think this was a RegEx issue that should now be fixed 😃
Thanks for taking a stab at it. I’ll let you know if we see issues in the future.