after upgrading my nuxt app to latest release I got an error when navigating to any page in SSR

[fahdaddi]

Hey @pi0, after upgrading my nuxt app to latest release I got an error when navigating to any page different than the home page, it shows the error: This page could not be found! while it was working perfectly in the nuxt@2.15

example of my pages config:

export default {
  home: {
    frFR: '/:amp?',
    frBE: '/:amp?',
    itIT: '/:amp?'
  },
  'about-us/legal-terms': {
    frFR: '/a-propos/mentions-legales/:amp?',
    frBE: '/a-propos/mentions-legales/:amp?',
    itIT: '/a-propos/mentions-legales/:amp?'
  },
}

Originally posted by @fahdaddi in #9010 (comment)

[danielroe]

Thanks for opening a new issue! Could you provide a reproduction? 🙏

[dewita97]

Hey, I also encountered this issue.

In my case, I have the nuxt-trailingslash-module in my buildModules that removes '/' at the end of an url. By removing this package from my modules, the app runs as it needs to be.

Try to investigate in your modules which one might not be compatible with the current version of Nuxt.

Regards :)

[alexcroox]

Not sure if related but since upgrading to the latest, one the generated bundle JS files is being loaded with an additional forward slash causing it to fail to load in production SSR:

https://example.com/public/admin-new-ModalNew/components/api-data/components/form-login/components/guard/components/guard-auth//f8c10e11-39ef08f02a9957807154.js

Notice the //f8c.. at the end ^^

Edit: Fixed by not using [name] in my build.filenames config

[pi0]

#8274 (comment)

[stale]

Thanks for your contribution to Nuxt!
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.
If you would like this issue to remain open:

1. Verify that you can still reproduce the issue in the latest version of nuxt-edge
2. Comment the steps to reproduce it

Issues that are labeled as pending will not be automatically marked as stale.