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
The dates that moment.js parses are not correctly localized anymore. This happens since the migration to vite as a bundler in #2321.
nextcloud/moment should normally load the correct localization on its own, which it did when the app was still build with webpack.
Since we switched to vite, the bundled moment version always uses the english locale. Weirdly, when executing moment in the javascript console, the correct locale is used (but that might be the global moment from server).
@susnux Do you have any idea what could go wrong with vite that the locale does not work anymore?
Example image:
The text was updated successfully, but these errors were encountered:
This seems to be related to tree shaking because the locales are not imported for moment thus they are removed. Fixed this on the nextcloud-moment package. See nextcloud-libraries/nextcloud-moment#781
The dates that moment.js parses are not correctly localized anymore. This happens since the migration to
vite
as a bundler in #2321.nextcloud/moment
should normally load the correct localization on its own, which it did when the app was still build withwebpack
.Since we switched to
vite
, the bundledmoment
version always uses the english locale. Weirdly, when executingmoment
in the javascript console, the correct locale is used (but that might be the global moment from server).@susnux Do you have any idea what could go wrong with
vite
that the locale does not work anymore?Example image:
The text was updated successfully, but these errors were encountered: