gatsby-plugin-i18n | Multi language routes for Gatsby | Frontend Framework library

by angeloocana JavaScript Version: Current License: No License

X-Ray Key Features Code Snippets Community Discussions(3)Vulnerabilities Install Support

kandi X-RAY | gatsby-plugin-i18n Summary

gatsby-plugin-i18n is a JavaScript library typically used in User Interface, Frontend Framework, React, Gatsby applications. gatsby-plugin-i18n has no bugs, it has no vulnerabilities and it has low support. You can download it from GitHub.

Multi language routes for Gatsby

Support

Quality

Security

License

Reuse

Support

gatsby-plugin-i18n has a low active ecosystem.

It has 424 star(s) with 77 fork(s). There are 10 watchers for this library.

It had no major release in the last 6 months.

There are 53 open issues and 26 have been closed. On average issues are closed in 29 days. There are 66 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of gatsby-plugin-i18n is current.

Quality

gatsby-plugin-i18n has 0 bugs and 0 code smells.

Security

gatsby-plugin-i18n has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

gatsby-plugin-i18n code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

gatsby-plugin-i18n does not have a standard license declared.

Check the repository for any license declaration and review the terms closely.

Without a license, all rights are reserved, and you cannot use the library in your applications.

Reuse

gatsby-plugin-i18n releases are not available. You will need to build from source code and install.

Installation instructions are not available. Examples and code snippets are available.

gatsby-plugin-i18n saves you 257 person hours of effort in developing the same functionality from scratch.

It has 624 lines of code, 0 functions and 74 files.

It has low code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of gatsby-plugin-i18n

Get all kandi verified functions for this library.

gatsby-plugin-i18n Key Features

No Key Features are available at this moment for gatsby-plugin-i18n.

gatsby-plugin-i18n Examples and Code Snippets

No Code Snippets are available at this moment for gatsby-plugin-i18n.

Community Discussions

Trending Discussions on gatsby-plugin-i18n

GatsbyJS + Firebase : initializeApp is not a function

How to create indexable i18n content dynamically from a CMS in Gatsby

How to change Markdown link relative path as preprocessing of gatsby-transformer-remark

QUESTION

GatsbyJS + Firebase : initializeApp is not a function

Asked 2018-Nov-03 at 14:38

I am totally stuck.

Have a setup of GatsbyJS 1 with gatsby-next and React 16 + latest Firebase 5.5.7

In develop mode everything works fine, but when I try to make a build I always get: WebpackError: _firebase2.default.initializeApp is not a function

I have already tried all of the following kinds if imports, and all of them result in this error: import firebase from 'firebase'; // const firebase = require('firebase/app') // import * as firebase from 'firebase'; var config = { ... }; firebase.initializeApp(config);

I have tried updating to the latest versions of all libraries. The only one I can't really update at the moment due to lots of migrations is GatsbyJS 2.0

Here is my package.json: "dependencies": { "@material-ui/core": "^3.2.2", "@material-ui/icons": "^3.0.1", "aws-sdk": "^2.345.0", "cookieconsent": "^3.0.6", "firebase": "^5.5.7", "firebaseui": "^3.4.1", "fsevents": "^1.2.4", "gatsby": "^1.9.279", "gatsby-link": "^1.6.46", "gatsby-plugin-google-analytics": "^1.0.20", "gatsby-plugin-i18n": "^0.4.1", "gatsby-plugin-react-helmet": "^1.0.8", "gatsby-plugin-react-next": "^1.0.11", "material-ui-chip-input": "^1.0.0-beta.8", "paypal-checkout": "^4.0.228", "react": "^16.5.2", "react-dom": "^16.5.2", "react-firebaseui": "^3.1.2", "react-intl": "^2.4.0", "reactstrap": "^6.5.0" },

For some time project was running fine on some older versions of libraries.

...

ANSWER

Answered 2018-Nov-03 at 14:38

Long story short, Firebase now includes Fetch polyfill that references self internally, so it doesn't work with gatsby.

Workaround would be to not load firebase using null-loader, but then you can't reference anything firebase-related during your build time, including properties for authentication providers

Issue seems to be limited to Gatsby v1 with Firebase 5.0.+

Rolling back to older version of Firebase is not possible due to an issue with pre-gyp and node version conflicts.

Posted a bug on: https://github.com/gatsbyjs/gatsby/issues/9681

Source https://stackoverflow.com/questions/53130971

QUESTION

How to create indexable i18n content dynamically from a CMS in Gatsby

Asked 2018-Jun-06 at 22:39

In my case I am trying to create SEO ready content from Contentful pulled into Gatsby. I've tried to integrate the community i18n plugin with the Contentful example here: https://github.com/mccrodp/gatsby-contentful-i18n/pull/1

I've seen the more general questions relating to i18n in Gatsby and the blog post Building i18n with Gatsby which does not use the community plugin, nor provide a linked repository example. However, I cannot understand how to integrate the community plugin gatsby-starter-default-i18n with dynamic content via a CMS, such as the Using Contentful Example.

I guess it boils down to how to manage layouts dynamically together with templates and the gatsby.node.js file, rather than the static example we have at the moment that does not use templates. An issue was raised here previously, on i18n plugin repo working with gatsby-source-contentful, but it seems inactive at the moment.

Any help greatly appreciated. I don't need to use the community plugin, just a SEO ready solution for indexed, dynamic i18n content paths. Thanks!

...

ANSWER

Answered 2018-Feb-20 at 09:16

This involves using node_locale in createPages fn in gatsby.node.js to set the locale based paths. Then you can use this in combination with dynamic sources. For example, I have created starter repos for markdownRemark and Contentful:

Source https://stackoverflow.com/questions/48757479

QUESTION

How to change Markdown link relative path as preprocessing of gatsby-transformer-remark

Asked 2018-Feb-19 at 10:36

I am developping a static blog using Gatsby. It use gatsby-transformer-remark and gatsby-plugin-i18n plugin to support multiple languages.

I am managing the articles in the GitHub repository as follows.

/blog
- /2017
  - /06
    - 01-foo.en.md
    - 01-foo.zh.md
  - /09
    - 01-bar.en.md
    - 01-bar.zh.md

And links between the articles is necessary. Therefore, in order not to become a dead link when looking at GitHub with a Web browser, we set up a link as follows.

...

ANSWER

Answered 2018-Feb-19 at 10:36

You can create a plugin for gatsby-transformer-remark

plugins/gatsby-remark-relative-linker/index.js:

Source https://stackoverflow.com/questions/48553146

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install gatsby-plugin-i18n

You can download it from GitHub.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: