react-datepicker: Module not found: Can't resolve 'react-datepicker/dist/react-datepicker.css' in v2.9.0

Describe the bug Looks like the package folder is missing dist folder after 2.9.0 release causing webpack build to fail due to the missing ‘react-datepicker/dist/react-datepicker.css’ file

To Reproduce Steps to reproduce the behavior:

Install 2.9.0 version and import ‘react-datepicker/dist/react-datepicker.css’ file in one of your components

Desktop (please complete the following information):

OS: Mac

Additional context Node: 12.9.0 NPM: 6.10.2

About this issue

Original URL
State: closed
Created 5 years ago
Reactions: 16
Comments: 31 (6 by maintainers)

Most upvoted comments

You need to install both “@types/react-datepicker” & “react-datepicker”

minhld-ows on Sep 26, 2022

getting this error on v2.10.1

izaakf on Dec 2, 2019

Thx @martijnrusschen ! All working now 💯

tuttiflirty on Aug 29, 2019

Can you try this again with v2.9.3?

martijnrusschen on Aug 29, 2019

same problem on @2.1.0. Hopefully you guys can resolve this)

JohnLyonJunior on Aug 29, 2019

@mxschmitt Any idea what went wrong here. This might be caused by the refactoring of the release process.

I guess it it’s because of my refactoring. I will investigate now

mxschmitt on Aug 29, 2019

Okay, kindly let me know does that different package has accessibility support?

Anyway, I did a workaround to fix this. Just moved the file node_modules/react-datepicker/dist/react-datepicker.css to my local src folder and imported it.

sommesh on May 2, 2020

Fixed by 98fa95162b51ac523da37c8de66fae05d64ef717. Thanks all!

martijnrusschen on Aug 29, 2019

I’m observing the same issue on @2.0.0 also. I managed to get rid of the problem locally with npm install style-loader css-loader --save but I still have this issue on Circle CI as

yarn run v1.17.3
$ react-scripts build
Creating an optimized production build...
Failed to compile.

Module not found: Error: Can't resolve 'react-datepicker/dist/react-datepicker.css' ...

tuttiflirty on Aug 29, 2019

@mxschmitt Any idea what went wrong here. This might be caused by the refactoring of the release process.

martijnrusschen on Aug 29, 2019