netlify[bot]
commented
11 months ago Deploy Preview for nuxt-gtag ready!
| Name | Link |
|---|---|
| Latest commit | e1cce494afc7dff05e3e6217b04424c5afded65b |
| Latest deploy log | https://app.netlify.com/sites/nuxt-gtag/deploys/65843a4b65a3920008775915 |
| Deploy Preview | https://deploy-preview-36--nuxt-gtag.netlify.app |
| Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site configuration.
johannschopplich
🔗 Linked issue
❓ Type of change
📚 Description
This is a 'canary' pull request. It aims to ensure that the ecosystem is ready for a shift in the default Nuxt TypeScript module resolution from 'Legacy' to 'Bundler': https://github.com/nuxt/nuxt/pull/24837. You'll need to run your build + type checking tests to verify that things still work; I'm hoping that CI will do that for us so we get an immediate indication of whether there's anything to investigate further here.
'Bundler' module resolution is recommended by Vue and by Vite, but unfortunately there are still many packages that do not have the correct entries in their
package.json.This might include this module or packages that are used by this module. You can see, for example: https://arethetypeswrong.github.io/?p=nuxt-gtag. The initial red X for
node10needs to be fixed in https://github.com/nuxt/module-builder; you can ignore that for now.If there are any errors reported in CI for this PR, it would be good to fix them for the sake of any users of this module who enable the Bundler module resolution. Feel free to ping me or others on the Nuxt Discord if you need any help resolving any issues discovered by this PR - and feel free to check out https://github.com/nuxt/nuxt/pull/24837 for any feedback or comments from others affected.
📝 Checklist