Exports broken for chips, drawer and textfield

[thdk]

Using the 0.41.0 version of the following packages:

• @material/chips
• @material/drawer
• @material/textfield
• ...

Gives the following errors when bundling:
Error: 'MDCChipSet' is not exported by node_modules@material\chips\dist\mdc.chips.js
Error: 'MDCDrawer' is not exported by node_modules@material\drawer\dist\mdc.drawer.js
Error: 'MDCTextField' is not exported by node_modules@material\textfield\dist\mdc.textfield.js

Downgrading to "0.40.1" is a temporary workaround.

What MDC Web Version are you using?

0.41.0

What is the expected behavior?

packages should export: MDCChipSet, MDCDrawer, MDCTextField

What is the actual behavior?

Build fails because of the missing exports

Any other information you believe would be useful?

There is already an issue for MDCSelect #4129 which I believe was facing the same problems as the packages listed above.

[kfranqueiro]

#4129 was caused by missing exports in mdc-select/index.js. However, all of the exports mentioned in this issue are present, and I'm unable to reproduce this issue.

I tested this JS, using the webpack config from our getting started guide:

import {MDCChip, MDCChipSet} from '@material/chips';
import {MDCDrawer} from '@material/drawer';
import {MDCTextField} from '@material/textfield';

console.log(MDCChip);
console.log(MDCChipSet);
console.log(MDCDrawer);
console.log(MDCTextField);

MDC Web packages listed in output of npm ls --depth 0:

├── @material/chips@0.41.0
├── @material/drawer@0.41.1
├── @material/textfield@0.41.0

Can you provide a gist or repository that reproduces this issue?

[thdk]

I have created a reduced repository where this error occurs:
https://github.com/thdk/mdctextfield-not-exported

run npm install and then run gulp

I'm using gulp with the gulp-stream plugin to bundle my files.

Let me know if I can be of any more help. Your time is appreciated.

As said earlier, updating package.json with the 0.40.1 version of @material/textfield does make the bundling work.

"dependencies": {
    "@material/textfield": "0.40.1"
  }

[williamernest]

You can resolve this issue by either adding /index to each of your import statements (recommended) or changing your imports to * as MDCCheckbox.

We could resolve this by adding "module": "index.js" to our package.json file so that rollup correctly resolves to the ES6 file, but IIRC we had a reason to not add that when we last updated our "main".

[thdk]

Thanks, that allowed me to upgrade indeed.

I used your first recommendation and added /index to each of my imports.

Is it likely that it will stay like this? Or do you think i can remove this suffix from my imports with later versions?

[kfranqueiro]

If your goal is to consume our modules in ES2015+ format, you should specifically reference index.js. We have a note about this in our getting started guide.

RE Will's comment, the reason for not specifying module was because even according to rollup's own docs, module is intended to point to something that is purely an ES2015 module with no other transforms necessary, which isn't completely true of our code (we also use babel's transform-object-assign plugin becuase IE11 doesn't support Object.assign).

[williamernest]

Closing this issue since the exports are working as intended.