Hi, I want to pass the locale to the query like below since I fetch data from contentful. How could I do it?

query Query($slug: String!, $language: String) {
  page: contentfulPage(slug: {eq: $slug}, node_locale: {eq: $language}) {
    ...pageMetaFields
    content {
   ...
    }
    node_locale
  }
}

I check the context and see that we already have the language there.

 {
  language: 'en-US',
  intl: {
    language: 'en-US',
    languages: [ 'en-US', 'ja' ],
    messages: { title: 'Gatsby English' },
    routed: false,
    originalPath: '/exp-postgresql/',
    redirect: false,
    redirectDefaultLanguageToRoot: true,
    defaultLanguage: 'en-US',
    ignoredPaths: []
  },
  slug: 'some-slug'
}

I try to pass the language but my query doesn't pick it up

export function onCreatePage({ page, actions }: CreatePageArgs) {
  const { createPage, deletePage } = actions;
  const slug = page.path.replace(/\//g, '') || '/';
  deletePage(page);

  createPage({ ...page, context: { 
    ...page.context, slug
   } });
}

hi
is it possible i can use ts file instead of json file so i can folder structure inside the scr/locale folder and then make a en.ts file instead of en.json file.

During building my project I see the following warning:
warn Plugin gatsby-plugin-react-intl is not compatible with your gatsby version 4.0.1 - It requires gatsby@^3.0.0

It is proposed to update the peerDependencies of the plugin as described in the doc: https://www.gatsbyjs.com/docs/reference/release-notes/migrating-from-v3-to-v4/#for-plugin-maintainers.

Hi, I just want to translate one of my pages. Could we have the includedPaths option? Thank you so much

Hello, i'm experimenting with your plugin and i have a request, if possible.

Is there a way to get the current locale in the URL?
For example:
I'm visiting the webite from Italy, so this

const intl = useIntl()
const lang = intl.locale

results in lang to be equal to it.

If i then navigate to /en/index, the lang variable remains equal to it.

What will be useful to me is a different variable (urlLocale ?) telling me the locale as per the URL, even if it is different from the user browser locale.

This way i can show english pages if the user "switches" language from the URL.

If the user disables cookies, the access of window.localStorage throws an exception, which prevents further rendering and simply results in white pages.

The code causing this issue:

• https://github.com/theowenyoung/gatsby-plugin-intl/blob/main/src/wrap-page.js#L70
• https://github.com/theowenyoung/gatsby-plugin-intl/blob/main/src/wrap-page.js#L90

Should be trivial to fix using a bit of try catch.

when I try to load a component with UI in wrapPageElements that uses useIntl, this fails saying that the component is not a decendant of IntlProvider;

instead of declare module 'gatsby-plugin-intl' it should be declare module 'gatsby-plugin-react-intl'

Hi,
I am having an issue on iOS13 which prevents the page from loading fully.
I tried on both mobile Safari and mobile Firefox, same result from the console :

Error: Cannot find react-intl/locale-data/fr

It looks like a polyfill issue with format.js
I switched to gatsby-plugin-intl (version ^0.3.3) and I am not getting the error anymore.

Since the original project seems to have been abandoned, and this one has enabled me to upgrade my projects to Gatsby v3 (thanks @theowenyoung!), I thought I would post this feature request here for discussion.

I would like to be able to skip generating root pages that have been replaced by the localized versions. This should be compatible with pages that are generated via gatsby-node.js (e.g., from a CMS) as well as file-based ones. At the same time, this feature would need to preserve root paths for pages that should not be localized, by respecting the new ignoredPaths setting. An example that comes up often in my work is a /blog/, which is rarely translated.

So in other words:

/about/ ❌
/en/about/ ✅
/de/about/ ✅
/services/ ❌
/en/services/ ✅
/de/services/ ✅
/blog/ ✅
/en/blog/ ❌
/de/blog/ ❌
etc…

Right now, generating these unwanted pages means ~33% of page queries are unnecessary (for a bilingual website), and build times are higher than they need to be (including superfluous image transformations, depending on the project setup). It also means that we need to be extra careful about duplicate content by excluding these pages from /sitemap.xml (which entails a lot of customization of the settings for plugins like gatsby-plugin-sitemap) – apart from the standard stuff like generating canonical meta tags.

What do you think? Is this something that is easily developed, or am I missing some caveats?