Unable to webpack compile after installing module

[duhmojo]

Hi. I haven't found any info or tips on my issue so I'm turning to you to see if this is a simple issue on my part. After I installed your typeahead module my webpack compile started to fail with the following:

ERROR in ./node_modules/react-bootstrap-typeahead/es/propTypes.js
Module not found: Error: Can't resolve './types' in '/home/duh/Development/verity/frontend/node_modules/react-bootstrap-typeahead/es'
 @ ./node_modules/react-bootstrap-typeahead/es/propTypes.js 4:0-31 18:52-56
 @ ./node_modules/react-bootstrap-typeahead/es/components/ClearButton.js
 @ ./node_modules/react-bootstrap-typeahead/es/index.js
 @ ./src/_complianceServicesProfiles/Profiles.jsx
 @ ./src/_complianceServicesProfiles/ComplianceServicesProfiles.jsx
 @ ./src/IrmPage/IrmPage.jsx
 @ ./src/IrmPage/index.js
 @ ./src/App/NavPage.jsx
 @ ./src/App/App.jsx
 @ ./src/App/index.js
 @ ./src/index.jsx

In my Component I just imported the css and module as instructed:

...
import 'react-bootstrap-typeahead/css/Typeahead.css';
import { Typeahead } from 'react-bootstrap-typeahead';

I'm not sure if the problem is related to Typeahead looking for Size from './types' while under /es/ as it looks like the types are under a directory back. .e.g there is no ./es/types. I'm unfamiliar with this detail and not sure if its something I should be configuring in Webpack. Any tips would be helpful as I'm unable to try your module at all right now.

For versions I'm using:

• "react": "16.13.1",
• "react-bootstrap": "^1.6.4",
• "react-bootstrap-typeahead": "^6.0.0-alpha.2",
  ...
• "html-webpack-plugin": "4.3.0",
• "url-loader": "4.1.0",
• "webpack": "4.43.0",
• "webpack-cli": "3.3.12",
• "webpack-dev-server": "3.11.0"

Thank you.

[ericgio]

Hey @duhmojo thanks for the report! There is a types.ts file in the source files. I instructed babel to ignore it when it transpiles the cjs and es modules, which is why you don't see it. However, that file contains a Size enum that is being called in propTypes.js and a few other places, which is triggering the error. I'll publish a new version with a fix.

[ericgio]

This should be resolved in v6.0.0-alpha.3

[harrylepotter-win]

Hey @ericgio - for some reason or other i still appear to be having this issue in 6.0.0-alpha.4

[ericgio]

@harrylepotter-win: Thanks for the report. I caused the same issue again with a change in v6.0.0-alpha.5 🤦

[ericgio]

Should be fixed in v6.0.0-alpha.6

[harrylepotter-win]

@ericgio many thanks! (...and thanks for the awesome component!)