Webpack Warning - There is another module with equal name when case is ignored about classnames HOT 8 CLOSED

I vote the AMD exports are removed entirely; then this is a non-issue.

from classnames.

probably better to keep it all lowercased classname.

from classnames.

Assuming most people have now switched to ES imports, why doesn't classnames have an ES6 main file using module key in package.json? module.exports can be mapped to ES in 2 different ways (wildcard import and default import) which causes issues if used in a complicated scenarios with typescript, babel, node etc.

from classnames.

Okay I investigated the issue more carefully. As it turns out it is quite simple.
Just use the CommonJS module key:

import classNames from 'classNames';

I leave it open, because inconsistency in module names for different module syntax is a bad practise.

from classnames.

probably better to keep it all lowercased classname.

Agreed, but that is now a massive breaking change for anyone using bower.

from classnames.

Agree, it is definitely a breaking change. So I would put it in a Major release.

from classnames.

The issue help me solve my problem.Thanks.

from classnames.

Probably resolved by #150, closing in favour of that (unless it isn't, in which case, re-open)

from classnames.