-
Notifications
You must be signed in to change notification settings - Fork 625
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Could not find a declaration file for module 'luxon' #688
Could not find a declaration file for module 'luxon' #688
Comments
You're absolutely right! Typescript cached a version of |
Yes, I had the same issue. 😄 Typescript cached the library on my local machine and I was scratching my head for 30 minutes about why it fails on the CI/CD server. |
If we'd add |
On the other hand |
I tried to install |
I'm sorry I made a mistake in my message, I meant |
I've made a PR to add |
No problem, thanks for the quick fix! |
## Description - added `@types/luxon` to dependencies - updated Luxon from `v3.2.1` to `v3.3.0` (avoided `v3.4.0` since types aren't available for that version yet). ## Related Issue Fixes #688. ## Motivation and Context This library needs to depend on `@types/luxon` since we now export our own types. See the related issue for the error this fixes. ## How Has This Been Tested? - checked that TypeScript now correctly loads the Luxon types - ran tests locally ## Types of changes - [X] Bug fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to change) ## Checklist: - [X] My code follows the code style of this project. - [ ] My change requires a change to the documentation. - [ ] I have updated the documentation accordingly. - [ ] I have added tests to cover my changes. - [X] All new and existing tests passed. - [ ] If my change introduces a breaking change, I have added a `!` after the type/scope in the title (see the Conventional Commits standard).
## [2.4.2](v2.4.1...v2.4.2) (2023-08-26) ### 🐛 Bug Fixes * **deps:** update dependency luxon to v3.3.0 & add [@types](https://github.com/types)/luxon ([#689](#689)) ([c95a449](c95a449)), closes [#688](#688)
🎉 This issue has been resolved in version 2.4.2 🎉 The release is available on: Your semantic-release bot 📦🚀 |
@SirAndrii thanks for reporting on this, let's track this here: #692 |
…ktiv#689) ## Description - added `@types/luxon` to dependencies - updated Luxon from `v3.2.1` to `v3.3.0` (avoided `v3.4.0` since types aren't available for that version yet). ## Related Issue Fixes kelektiv#688. ## Motivation and Context This library needs to depend on `@types/luxon` since we now export our own types. See the related issue for the error this fixes. ## How Has This Been Tested? - checked that TypeScript now correctly loads the Luxon types - ran tests locally ## Types of changes - [X] Bug fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to change) ## Checklist: - [X] My code follows the code style of this project. - [ ] My change requires a change to the documentation. - [ ] I have updated the documentation accordingly. - [ ] I have added tests to cover my changes. - [X] All new and existing tests passed. - [ ] If my change introduces a breaking change, I have added a `!` after the type/scope in the title (see the Conventional Commits standard).
## [3.0.0-beta.4](v3.0.0-beta.3...v3.0.0-beta.4) (2023-09-10) ### 🐛 Bug Fixes * **deps:** update dependency luxon to v3.3.0 & add [@types](https://github.com/types)/luxon ([#689](#689)) ([c95a449](c95a449)), closes [#688](#688) * fix range parsing when upper limit = 0 ([#687](#687)) ([d96746f](d96746f)) ### 🚨 Tests * add TS types check ([#690](#690)) ([f046016](f046016))
🎉 This issue has been resolved in version 3.0.0-beta.4 🎉 The release is available on: Your semantic-release bot 📦🚀 |
## [2.4.2](kelektiv/node-cron@v2.4.1...v2.4.2) (2023-08-26) ### 🐛 Bug Fixes * **deps:** update dependency luxon to v3.3.0 & add [@types](https://github.com/types)/luxon ([#689](kelektiv/node-cron#689)) ([c95a449](kelektiv/node-cron@c95a449)), closes [#688](kelektiv/node-cron#688)
## Description - added `@types/luxon` to dependencies - updated Luxon from `v3.2.1` to `v3.3.0` (avoided `v3.4.0` since types aren't available for that version yet). ## Related Issue Fixes #688. ## Motivation and Context This library needs to depend on `@types/luxon` since we now export our own types. See the related issue for the error this fixes. ## How Has This Been Tested? - checked that TypeScript now correctly loads the Luxon types - ran tests locally ## Types of changes - [X] Bug fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to change) ## Checklist: - [X] My code follows the code style of this project. - [ ] My change requires a change to the documentation. - [ ] I have updated the documentation accordingly. - [ ] I have added tests to cover my changes. - [X] All new and existing tests passed. - [ ] If my change introduces a breaking change, I have added a `!` after the type/scope in the title (see the Conventional Commits standard).
## [2.4.2](v2.4.1...v2.4.2) (2023-08-26) ### 🐛 Bug Fixes * **deps:** update dependency luxon to v3.3.0 & add [@types](https://github.com/types)/luxon ([#689](#689)) ([c95a449](c95a449)), closes [#688](#688)
…ktiv#689) ## Description - added `@types/luxon` to dependencies - updated Luxon from `v3.2.1` to `v3.3.0` (avoided `v3.4.0` since types aren't available for that version yet). ## Related Issue Fixes kelektiv#688. ## Motivation and Context This library needs to depend on `@types/luxon` since we now export our own types. See the related issue for the error this fixes. ## How Has This Been Tested? - checked that TypeScript now correctly loads the Luxon types - ran tests locally ## Types of changes - [X] Bug fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to change) ## Checklist: - [X] My code follows the code style of this project. - [ ] My change requires a change to the documentation. - [ ] I have updated the documentation accordingly. - [ ] I have added tests to cover my changes. - [X] All new and existing tests passed. - [ ] If my change introduces a breaking change, I have added a `!` after the type/scope in the title (see the Conventional Commits standard).
## [2.4.2](kelektiv/node-cron@v2.4.1...v2.4.2) (2023-08-26) ### 🐛 Bug Fixes * **deps:** update dependency luxon to v3.3.0 & add [@types](https://github.com/types)/luxon ([kelektiv#689](kelektiv#689)) ([c95a449](kelektiv@c95a449)), closes [kelektiv#688](kelektiv#688)
…ktiv#689) ## Description - added `@types/luxon` to dependencies - updated Luxon from `v3.2.1` to `v3.3.0` (avoided `v3.4.0` since types aren't available for that version yet). ## Related Issue Fixes kelektiv#688. ## Motivation and Context This library needs to depend on `@types/luxon` since we now export our own types. See the related issue for the error this fixes. ## How Has This Been Tested? - checked that TypeScript now correctly loads the Luxon types - ran tests locally ## Types of changes - [X] Bug fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to change) ## Checklist: - [X] My code follows the code style of this project. - [ ] My change requires a change to the documentation. - [ ] I have updated the documentation accordingly. - [ ] I have added tests to cover my changes. - [X] All new and existing tests passed. - [ ] If my change introduces a breaking change, I have added a `!` after the type/scope in the title (see the Conventional Commits standard).
## [2.4.2](kelektiv/node-cron@v2.4.1...v2.4.2) (2023-08-26) ### 🐛 Bug Fixes * **deps:** update dependency luxon to v3.3.0 & add [@types](https://github.com/types)/luxon ([kelektiv#689](kelektiv#689)) ([c95a449](kelektiv@c95a449)), closes [kelektiv#688](kelektiv#688)
…ktiv#689) ## Description - added `@types/luxon` to dependencies - updated Luxon from `v3.2.1` to `v3.3.0` (avoided `v3.4.0` since types aren't available for that version yet). ## Related Issue Fixes kelektiv#688. ## Motivation and Context This library needs to depend on `@types/luxon` since we now export our own types. See the related issue for the error this fixes. ## How Has This Been Tested? - checked that TypeScript now correctly loads the Luxon types - ran tests locally ## Types of changes - [X] Bug fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to change) ## Checklist: - [X] My code follows the code style of this project. - [ ] My change requires a change to the documentation. - [ ] I have updated the documentation accordingly. - [ ] I have added tests to cover my changes. - [X] All new and existing tests passed. - [ ] If my change introduces a breaking change, I have added a `!` after the type/scope in the title (see the Conventional Commits standard).
Description
The following error message is thrown from the cron module (using Typescript):
The issue is caused by a missing type definition for the luxon library. The docs for the library states it should be installed as a developer dependency separately for typescript.
Screenshots
Additional information
No response
The text was updated successfully, but these errors were encountered: