react-cookies | : cookie : Load and save cookies with React | Frontend Framework library

The accesstoken is an httpOnly cookie. The httpOnly flag ensures that the cookie cannot be accessed by client-side javascript.

You can disable the httpOly flag on the accesstoken to make it accessible.

An alternative is getting the access token from the API and setting it in localstorage, which is the most common I've seen.

You can try and search online on how to store accesstoken in react app

Didn't find a permanent solution, but found a fix...

The problem stemmed from a conflict between my gatsby-source-wordpress and the way my Polylang WP plugin gets exposed to the GraphQL API. Basically, the "Duplicate ID" is related to the first post the API could find that has a translation, and for some reason it breaks. As of this writing this seems to be specific to gatsby-source-wordpress version ^5.0.0 and ^5.1.0. My fix : revert to gatsby-source-wordpress version ^4.1.0-next.1, which does not suffer from the same issue.

This fix works for me with Gatsby v3.1.1.

The reason you are getting this error is because one of your dependencies (or maybe even your code) relies on React.createContext method.

This is part of the "context API" introduced in version 16.3 (changelog)

You either have to remove the dependency that requires this later react version, or upgrade your react version to at least 16.3.

Typically, when a dependency in your package.json depends on a specific version of react, it would list that version as a "peer dependency". If so, when running npm install you would receive a warning that looks like

For getting the cookie, instead of using library you can write a function and pass the key name.

Flow syntax is not real JS. so things like type Props will fall apart when transpiling or bundling. You need to add a babel plugin/preset to handle these cases.

This is what you're looking to add: https://babeljs.io/docs/en/babel-preset-flow

But specifically, Install @babel/preset-flow with either yarn or npm

Then in your .babelrc update your config to add the new preset

The issue is state comparisons are shallow, meaning, in the case of an object only the reference will be compared.

In your example, you update the cartItems property but not the object instance, so as far as React is concerned the state hasn't changed because it won't check individual properties.

Try creating a completely new cart each time and you should see the UI update e.g.