universse/gatsby-plugin-zeit-now

Enhancing Zeit Now zero-config deployments.

gatsby-plugin-zeit-now's Issues

Adding this plugin breaking tawk integration

After adding this plugin tawk(online support chat) integration is breaking. Widget works in dev mode, local build, but after deploying to Zeit it disappears.

redirects support

Hello,

Right now, I'm using now.json to keep a list of redirects:

{
  "redirects": [
    {
      "source": "/docs",
      "destination": "/docs/api/getting-started/overview"
    }
  ]
}

Could be possible do the same but using the plugin interface? That's what I'm suggesting:

plugins: [
  {
    resolve: 'gatsby-plugin-zeit-now',
    options: {
      redirects: [{
        source: "/docs",
        destination: "/docs/api/getting-started/overview"
      }]
    }
  }
]

Client routes created for react-intl

Hi, I'm using your plugin together with the gatsby-plugin-intl one and I notice a fake 404 response when I refresh a page from a language route like the homepage /en/.

I saw in the created __now_routes_g4t5bY.json json file that these extra rules are added:

{
    "src": "/en/.*",
    "dest": "/en/404/"
},
{
    "src": "/it/.*",
    "dest": "/it/404/"
}

from the client side routes generation... causing the above issue.
How can I avoid to add them?

thanks

PS: I can't find how your file __now_routes_g4t5bY.json is read by now... is it a naming convention?

Move from deprecated routes to redirects/rewrites

Vercel docs indicate that routes are now considered legacy, and by my testing Gatsby splat redirects don't work with routes regex.

I believe switching to redirects/rewrites will fix splats too.

gatsby-plugin-zeit-now not compatible with Gatsby version 3

When building with latest version of Gatsby I see this warning:

warn Plugin gatsby-plugin-zeit-now is not compatible with your gatsby version 3.7.1 - It requires gatsby@^2.0.0