You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
The module seems to be missing some typings for InclusiveDates elements.
Reproduction
Steps to reproduce the behavior:
npm install inclusive-dates
Navigate to node_modules/inclusive-dates/dist/components/index.d.ts
See error 'cannot find module' on line 2.
Expected behavior
The inclusive-dates module should include a dist/types/components/inclusive-dates folder with typings.
Screenshots
Context
I'm bundling inclusive-dates into a React component library to backbone a DatePicker component.
I did pull down the inclusive-dates repo and noticed that without adjusting any config, I built the library twice. After the first build, the dist folder looked exactly like what I pulled down from npmjs. After the second build, the dist folder updated to include all the typings. When I copied that locally built dist folder into my component library's assets folder and used inclusive-dates from there, it worked perfectly.
The text was updated successfully, but these errors were encountered:
Describe the bug
The module seems to be missing some typings for InclusiveDates elements.
Reproduction
Steps to reproduce the behavior:
npm install inclusive-dates
Expected behavior
The inclusive-dates module should include a dist/types/components/inclusive-dates folder with typings.
Screenshots
Context
I'm bundling inclusive-dates into a React component library to backbone a DatePicker component.
I did pull down the inclusive-dates repo and noticed that without adjusting any config, I built the library twice. After the first build, the dist folder looked exactly like what I pulled down from npmjs. After the second build, the dist folder updated to include all the typings. When I copied that locally built dist folder into my component library's assets folder and used inclusive-dates from there, it worked perfectly.
The text was updated successfully, but these errors were encountered: