nuxt-community / netlify-files-module

Nuxt 2 module to create new _headers, _redirects and netlify.toml files for Netlify or to use existing ones
MIT License
50 stars 5 forks source link

Nuxt 3 Support #41

Open harlan-zw opened 9 months ago

harlan-zw commented 9 months ago

Hey :wave: It looks like this module hasn't been updated for Nuxt 3. In an effort to improve the developer experience of modules, I've updated the module to clarify that it only supports Nuxt 2.

If Nuxt 3 support is added it will be moved to the https://github.com/nuxt-modules organisation.

Alternatives:

@manniL Are there any plans to upgrade to Nuxt 3, if not do you have any recommendations for users?

manniL commented 9 months ago

Not planned as it is not necessary in Nuxt 3. Nitro does cover the _redirects and _headers files pretty well 👍

DreaMinder commented 8 months ago

@manniL Nitro doesn't support Netlify's "200 status code" for proxying, :splat marker for wildcard routes, and "force" flag for overriding existing pages with redirects. It also overrides _redirects file that I created programmatically with a similar module. Just saying that even though Nitro has some cool integrations, there's still demand for such a module 🙌

manniL commented 8 months ago

Nitro doesn't support Netlify's "200 status code" for proxying, :splat marker for wildcard routes, and "force" flag for overriding existing pages with redirects.

You should be able to create your own _redirects until these features (e.g. https://github.com/unjs/nitro/issues/1748) are supported 👍 Please raise other issues if there are none

It also overrides _redirects file that I created programmatically with a similar module.

This should not happen, Nitro should only add to these files if they exist 🤔

DreaMinder commented 8 months ago

This should not happen, Nitro should only add to these files if they exist

I figured it out. I tried to write into .output/public which worked locally. But for some reason, netlify preset writes directly into dist and fails to build if dist is a symlink. It's working with dist target, sorry for bothering. 😓