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.

Conflicting Namespaces

See original GitHub issue

Type of Issue

[ x] Bug Report

Description

ole@mkt:~/Github/validatorjs-workspace$ npm run p

WARNING: Conflicting namespaces: dist/validatorts/esm2015/public-api.js re-exports ‘ɵ0’ from both dist/validatorts/esm2015/lib/validators/isIdentityCard.js and dist/validatorts/esm2015/lib/validators/isISO8601.js (will be ignored)

validatorjs-workspace@0.0.0 p /home/ole/Github/validatorjs-workspace cd projects/validatorts && bump patch && cd …/… && npm run b && cd dist/validatorts && npm publish

✔ Updated package.json to 12.2.30 ✔ Updated package-lock.json to 12.2.30

validatorjs-workspace@0.0.0 b /home/ole/Github/validatorjs-workspace ng build validatorts

Building Angular Package

Building entry point ‘@fireflysemantics/validatorts’

Compiling TypeScript sources through ngc Bundling to FESM2015 WARNING: Conflicting namespaces: dist/validatorts/esm2015/public-api.js re-exports ‘ɵ0’ from both dist/validatorts/esm2015/lib/validators/isIdentityCard.js and dist/validatorts/esm2015/lib/validators/isISO8601.js (will be ignored) Bundling to FESM5 WARNING: Conflicting namespaces: dist/validatorts/esm5/public-api.js re-exports ‘ɵ0’ from both dist/validatorts/esm5/lib/validators/isIdentityCard.js and dist/validatorts/esm5/lib/validators/isISO8601.js (will be ignored)

How To Reproduce

git clone https://github.com/fireflysemantics/validatorts
cd validatorts
npm run u
npm run p

$ node_modules/.bin/ng-packagr --version

ng-packagr: 9.0.2 @angular/compiler: 9.0.4 rollup: 1.31.1 tsickle:
typescript: 3.7.5

Issue Analytics

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

Top GitHub Comments

2reactions

jupin-rcommented, Mar 27, 2020

I have same issue. Conflict is for constant which is not exported.

0reactions

github-actions[bot]commented, Nov 13, 2022

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

_{This action has been performed automatically by a bot.}

Top Results From Across the Web

How to solve two conflicting namespaces with the same name

Try turning your core namespace into a sub namespace. EDIT: Cleaned up answer and added code. (Hard to do on mobile!)

Handle Conflicting Namespaces with Aliases

Handle Conflicting Namespaces with Aliases. Every once in a long while, I have a class name that appears in two different namespaces (there ......

2.9 — Naming collisions and an introduction to namespaces

This error is generally referred to as a naming collision (or naming conflict). If the colliding identifiers are introduced into the same file, ......

c# - Avoiding conflicting namespace and class name

You can resolve the namespace problem both in this case and in principle by providing a more comprehensive name to the namespace. No...

Fix inconsistent namespace naming - ReSharper - JetBrains

Fix inconsistent namespace naming · ReSharper quick-fix to synchronize namespace to the file location · ReSharper helps fix namespaces in a project.