fix(ui): upgrade base layer to Nuxt 4 and DevTools - #1785
Conversation
|
@Jacky-Pham we already have a JIRA ticket for upgrading to Nuxt v4. 3.x reached official End of Life (EOL) on July 31, 2026. |
|
Jacky-Pham
changed the title
| module.exports = { | ||
| content: ['**.{html,ts,js,vue}'], | ||
| presets: [require('@daxiom/nuxt-core-layer-test/tailwind.config')], | ||
| presets: [require('@daxiom/nuxt-core-layer-test/tailwind.config').default], |
There was a problem hiding this comment.
is this change necessary
There was a problem hiding this comment.
yes, this is needed. without .default this line does not load the actual tailwind settings. it still worked because nuxt was loading them somewhere else too, but we should not rely on that. this keeps the existing setup and makes sure it loads the right settings.
| '@nuxt/test-utils/module', | ||
| '@nuxt/image', | ||
| '@zadigetvoltaire/nuxt-gtm', | ||
| 'nuxt-gtag' |
There was a problem hiding this comment.
why is this module removed from this list?
There was a problem hiding this comment.
it was removed because this module only supports nuxt 3. for nuxt 4 we now use the same tracking package directly, so the setup stays the same without relying on the old module.
2 participants
Issue:
Description of changes:
3.15.4to4.5.2@nuxt/devtoolsfrom3.1.1to3.4.1strr-base-webpnpm lockfile and pin the upgraded packagesThese changes move the shared STRR base layer to the supported Nuxt 4 release line and address the applicable Nuxt and DevTools security alerts.
Note:
PR #1781 separately updates pnpm and may require a lockfile rebase depending on merge order.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of the BC Registry and Digital Services BSD 3-Clause License