Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

routeRules stopped working in 2.9 when deployed to Azure #2342

Closed
tobiasdiez opened this issue Apr 6, 2024 · 1 comment
Closed

routeRules stopped working in 2.9 when deployed to Azure #2342

tobiasdiez opened this issue Apr 6, 2024 · 1 comment

Comments

@tobiasdiez
Copy link
Contributor

Environment

  • Operating System: Windows_NT
  • Node Version: v21.7.2
  • Nuxt Version: 3.11.2
  • CLI Version: 3.11.1
  • Nitro Version: 2.8.1
  • Package Manager: yarn@3.6.3
  • Builder: -
  • User Config: future, alias, nitro, experimental, vue, hooks, app, modules, runtimeConfig, routeRules, tailwindcss, graphqlServer, content, site, vite
  • Runtime Modules: @nuxtjs/tailwindcss@6.11.4, @bg-dev/nuxt-naiveui@1.12.2, @pinia/nuxt@0.5.1, nuxt-graphql-server@3.0.0, @nuxt/content@2.12.1, storybook-vue-addon/nuxt, @nuxt/devtools@1.1.5, nuxt-icon@0.6.10,
    @vee-validate/nuxt@4.12.6, @nuxt/test-utils/module@3.12.0, @nuxtjs/seo@2.0.0-rc.10
  • Build Modules: -

Reproduction

JabRef/JabRefOnline#2370 not really a "minimal reproduction" but since there are issues with the deployment of the nitro example in https://github.com/unjs/nitro-deploys, I'm not sure where I should start

Describe the bug

After the upgrade from nitro 2.8.1 to 2.9.0 (or 2.9.6) all routes defined in nuxt.config as well as all pages except for the index are resulting in 404 errors when deployed to azure functions. Strangely, also the server routes are working correctly (in my case /api). I cannot reproduce it locally with the azure cli, and running the dev server locally also works. No errors are logged in the azure portal. Hence, I have no idea how to investigate this issue further.

If you have any idea what change could have triggered this, can try it again with a patched version.

Additional context

Perhaps nuxt/nuxt#26567 is related

Logs

No response

@tobiasdiez
Copy link
Contributor Author

Seems to be working now.

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

No branches or pull requests

1 participant