[Question] is it possible to have separate ES modules exports about classnames HOT 8 CLOSED

@dcousens Thanks for looking. Actually it is very simple if you care. You have each js file with import and export. Before publishing you use tool like rollup or babel to convert modules to UMD format used now (actually amd defined bad).
For other people comming there you can use for now classnames-es package.

from classnames.

webpack hack to add exports.default:

webpack.config.module.rules.push({ test: /classnames/, use: ['exports-loader?default=module.exports'] })

from classnames.

I was having problems importing this module into TypeScript for this very reason. Changing the export code in this library to the following fixes it:

		Object.defineProperty(exports, "__esModule", { value: true });
		exports.default = classNames;

Now I can import with:

import classnames from 'classnames';

But I have to add the compiler flag --allowSyntheticDefaultImports to make that work, because the TypeScript definitions don't declare a default export.

Related to #103

from classnames.

@btd do you mean you want a copy of the library using export/import?
I don't think that will be a simple thing to maintain... at all

from classnames.

Before publishing you use tool like rollup or babel to convert modules to UMD format used now (actually amd defined bad).

And there is the kicker. That isn't simple, and can be a pain to keep up to date.

from classnames.

For other people comming there you can use for now classnames-es package.

@btd maybe you can make a PR to put that in the README?

from classnames.

Unless @JedWatson (or @btd) wants to make a classnames/es file.

from classnames.

@jedmao You can use classnames in TypeScript without --allowSyntheticDefaultImports like this:

import * as cx from "classnames"

from classnames.