This lets npm install the latest versions of both date-fns and date-fns-tz. Recently a version 3 of date-fns has been released which introduced a lot of breakting changes in the file structure, and currently there are no versions of date-fns-tz that support these changes.
This means that currently a project using Kirby will not be able to build, unless an older date-fns version is specified in either the project or one of the other dependencies.
Describe how to reproduce the bug
Create a new project.
Install latest Kirby version.
Run the application.
Errors regarding files imported from date-fns are thrown by date-fns-tz.
Which Kirby version was used?
8.11.2 and 9.0.0-rc
What was the expected behavior?
The project runs.
Please complete the following information:
OS: MacOS
Browser: Chrome
Browser version: 120.0.6099.109
Checklist:
The following tasks should be carried out in sequence in order to follow the process of contributing correctly.
Verification
To make sure the bug is not intended behaviour; it should be verified by a member of team Kirby before moving on to implementation.
[ ] Make sure the NOT verified label has been removed by a member of team Kirby; do not proceed until this is done
Implementation
The contributor who wants to implement this issue should:
Describe the bug
When installing Kirby in a project its peer dependencies in the project's package-lock.json file get specified like this:
This lets npm install the latest versions of both
date-fns
anddate-fns-tz
. Recently a version 3 ofdate-fns
has been released which introduced a lot of breakting changes in the file structure, and currently there are no versions ofdate-fns-tz
that support these changes. This means that currently a project using Kirby will not be able to build, unless an olderdate-fns
version is specified in either the project or one of the other dependencies.Describe how to reproduce the bug
date-fns
are thrown bydate-fns-tz
.Which Kirby version was used?
8.11.2 and 9.0.0-rc
What was the expected behavior?
The project runs.
Please complete the following information:
Checklist:
The following tasks should be carried out in sequence in order to follow the process of contributing correctly.
Verification
To make sure the bug is not intended behaviour; it should be verified by a member of team Kirby before moving on to implementation.
NOT verified
label has been removed by a member of team Kirby; do not proceed until this is doneImplementation
The contributor who wants to implement this issue should:
Review
Once the issue has been implemented and is ready for review: