Skip to content

Conversation

@dependabot
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Nov 4, 2025

Bumps @vuepic/vue-datepicker from 11.0.2 to 12.0.1.

Release notes

Sourced from @​vuepic/vue-datepicker's releases.

v12.0.1

🐛 Bug Fixes

  • Fixed issue where text-input format pattern not propely inheriting default value from formats (#1172)
  • Fixed issue where selecting more that one date in multi-dates mode throws an error (#1173)

v11.0.3

🐛 Bug Fixes

v12.0.0

⚠️ Breaking changes

This release includes a lot of internal refactor and a lot of breaking changes.

Please take a look at the migration guide

🚀 Features

  • Added option to add calendard instance in setMonthYear exposed function (#1120)
  • Added option to hide menu arrow (floating prop) (#1089)
  • Added option to change inputmode (#1149)
  • Added option to set custom input id (input-attrs prop) (#1163)
  • Added @invalid event that propagates oninvalid from the input field (#1127)
  • Added input masking on text-input alpha stage , tnx to @​apsisxcoder (#1131)
  • Added support for rounding the value on now button (action-row prop) (#1138)

🐛 Bug Fixes

  • Fixed issue where time values in the overlay are not reacting to v-model change (#1108)
  • Fixed issue with time increment when picking from non-DST to DST date (#1112)
  • Fixed issue with being unable to use auto-apply when partialRange is enabled (#1113)
  • Fixed issue where Increasing calendar width makes the inline time picker not centered (#1117)
  • Fixed issue where maxRange and minRange are not working in year-picker mode (#1123)
  • Fixed issue where mobile swipe causes an unwanted selection of dates in the calendar (#1124, #1169)
  • Fixed issue where auto-apply closes the picker when using flow with range (#1125)
  • Fixed issue where start-date is not working in quarter-picker mode (#1133)
  • Fixed issue where events range-start and range-end are not emitted when the time is updated (fixes #1142)
  • Fixed positioning issue on smaller screens with preset-dates enabled (#1144)
  • Fixed issue with wrong week numbers from 2027 (#1147)
  • Fixed isue where auto-apply not selecting range in quarter-picker mode (#1166)

... (truncated)

Commits
  • 53b37d0 docs: Update docs build
  • 0f224fd chore: Resolve types
  • 2f869f1 chore: Bump version
  • c9125d7 docs: Try to resolve hydration issue on demo components
  • 6f2b19b fix: text-input prop using default patterns instead of format default (fixe...
  • 042b968 fix: Selecting more than one date in multi-dates throws an error (fixes #1173)
  • b6cf6ff docs: Add note for start-time in migration guide (fixes #1170)
  • c270fe1 docs: Fix examples for disabled-dates and allowed-dates (fixes #1171)
  • 8680cdf chore: Update readme
  • a39f8d7 chore: Update sonar workflow
  • Additional commits viewable in compare view

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

@dependabot dependabot bot added 3. to review Waiting for reviews dependencies Pull requests that update a dependency file labels Nov 4, 2025
@susnux
Copy link
Contributor

susnux commented Nov 4, 2025

@dependabot rebase

Bumps [@vuepic/vue-datepicker](https://github.com/Vuepic/vue-datepicker) from 11.0.2 to 12.0.1.
- [Release notes](https://github.com/Vuepic/vue-datepicker/releases)
- [Changelog](https://github.com/Vuepic/vue-datepicker/blob/main/CHANGELOG.md)
- [Commits](Vuepic/vue-datepicker@v11.0.2...v12.0.1)

---
updated-dependencies:
- dependency-name: "@vuepic/vue-datepicker"
  dependency-version: 12.0.1
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot force-pushed the dependabot/npm_and_yarn/vuepic/vue-datepicker-12.0.1 branch from 9070e26 to 7c6bf4c Compare November 4, 2025 12:11
@susnux susnux requested a review from ShGKme November 4, 2025 12:57
@codecov
Copy link

codecov bot commented Nov 4, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
⚠️ Please upload report for BASE (main@7020545). Learn more about missing BASE report.
⚠️ Report is 52 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #7767   +/-   ##
=======================================
  Coverage        ?   51.58%           
=======================================
  Files           ?       96           
  Lines           ?     3148           
  Branches        ?      865           
=======================================
  Hits            ?     1624           
  Misses          ?     1276           
  Partials        ?      248           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@dependabot @github
Copy link
Contributor Author

dependabot bot commented on behalf of github Nov 6, 2025

A newer version of @​vuepic/vue-datepicker exists, but since this PR has been edited by someone other than Dependabot I haven't updated it. You'll get a PR for the updated version as normal once this PR is merged.

@susnux susnux requested a review from Antreesy November 6, 2025 11:08
ShGKme

This comment was marked as resolved.

@ShGKme
Copy link
Contributor

ShGKme commented Nov 6, 2025

Item Initial Size Async Size Assets Size Total Size
components/NcDateTimePicker (before) 282.93 kb - 58.83 kb 341.76 kb
components/NcDateTimePicker (after) 887.21 kb - 58.90 kb 946.11 kb
diff 🔺+214% - ~ 🔺+177%

😬😬😬

} from '@nextcloud/l10n'
import VueDatePicker from '@vuepic/vue-datepicker'
import { VueDatePicker } from '@vuepic/vue-datepicker'
import * as locales from 'date-fns/locale'
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Instead of bundling an entire date-fns/locale bundle, can we check the current locale in runtime, async load only the used locale and then render the component with the used locale?
On open, if possible...

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done

Copy link
Contributor

@ShGKme ShGKme left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Some breaking changes seem to be missing.

Component was large already (13th largest) but now it is 3 times larger.

@AndyScherzinger AndyScherzinger self-requested a review November 6, 2025 20:14
@susnux susnux requested a review from ShGKme November 6, 2025 20:25
@susnux
Copy link
Contributor

susnux commented Nov 6, 2025

Some breaking changes seem to be missing.

resolved that part and size should also be resolved.

@ShGKme
Copy link
Contributor

ShGKme commented Nov 7, 2025

Tested in both Vite and Webpack apps?

@susnux
Copy link
Contributor

susnux commented Nov 7, 2025

Tested in both Vite and Webpack apps?

Currently only tested it in vite apps

@susnux
Copy link
Contributor

susnux commented Nov 7, 2025

Pushed a fix, should now work as expected in both app classes.

Comment on lines +10 to +11
// this is a fix only for the styleguide as webpack does not have glob import
let modules: Record<string, () => Promise<{ default: Locale }>>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Webpack does have glob import

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we need it in a shared util if this is only used by a single component (for its internal dependency)?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Basically just to clean the component

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, but was discussed in another PR, if this is not a shared util, but only a part of NcDateTimePicker, it can be placed in components/NcDateTimePocker.

@ShGKme
Copy link
Contributor

ShGKme commented Nov 10, 2025

Better than with bundling everything. But still quite large. I guess, there is notthing we can do with it.

Item Initial Size Async Size Assets Size Total Size
components/NcDateTimePicker (before) 282.93 kb - 58.83 kb 341.76 kb
components/NcDateTimePicker (after) 315.34 kb 1840.26 kb 58.90 kb 2214.50 kb
diff 🔺+12% - ~ 🔺+550%

@ShGKme
Copy link
Contributor

ShGKme commented Nov 10, 2025

One problem I found. With default Vite and some Webpack/RSPack configs, every locale as well as its shared utils (3 modules) are new chunks. It increases number of chunks in an app significantly. And some locales needs ~4 HTTP requests.

It is solvable by local bundler config, for example, by setting a new cacheGroup.

However, because these chunks are just mixed with others, it's a bit hard, requires regexp to find very specific files in node_modules.

Can we:

  1. Either not bundle these modules and keep it in data-fns
  2. Or build them into a split folder in nextcloud-vue with a predictable path.

@susnux
Copy link
Contributor

susnux commented Nov 11, 2025

every locale as well as its shared utils (3 modules) are new chunks. It increases number of chunks in an app significantly.

Well but thats a good thing here if every locale is its own chunk then the user only loads what needed - the locale will mostly not change so only the needed chunk is loaded.
The number of chunks is currently not a performance issue but the size of them is the current real performance issue.

Nevertheless I currently check if we can avoid date-fn locales here in general as we already pass in most of the formatting our self.

@ShGKme
Copy link
Contributor

ShGKme commented Nov 11, 2025

Well but thats a good thing here if every locale is its own chunk then the user only loads what needed - the locale will mostly not change so only the needed chunk is loaded.
The number of chunks is currently not a performance issue but the size of them is the current real performance issue.

In general, it is also an issue. Having too many nano chunks instead of web-optimised is one of the reasons Rollup to be developed.

I did not propose to have no chunk, but only to have 1 chunk per locale. It doesn't make sense to load 4 chunks just to have a single locale in a date-time picker.

Anyway, that is not the main, but only an additional problem.

The main problem is that date-fns locales now live not separately in date-fns/locale, but in @nextcloud/vue/dist/chunks mixed with all the other chunks.

This makes it quite complicated to configure any date-fns specific bundling for the library user.

They are different from other "classic" chunks and may require specific handling.

For example, we never need to have more than 1 locale. It is always a single locale. Thus it doesn't make sense to merge locale chunks into other modules even if they are too small, unlike normal chunks.

@ShGKme
Copy link
Contributor

ShGKme commented Nov 11, 2025

Briefly, I'd prefer:

  • Either keep date-fns locales in the date-fns and not distribute it as @nextcloud/vue own chunks
  • Or split them at least structurally so a developer can configure locale handling on the app side

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

3. to review Waiting for reviews dependencies Pull requests that update a dependency file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants