gatsbycentral / gatsby-source-eventbrite Goto Github PK

There have been updates to the gatsby monorepo:

• • The dependency gatsby-plugin-sharp was updated from 2.0.28 to 2.0.29.

• The dependency gatsby-source-filesystem was updated from 2.0.26 to 2.0.27.
• The peerDependency gatsby was updated from 2.1.33 to 2.1.34.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

This monorepo update includes releases of one or more dependencies which all belong to the gatsby group definition.

gatsby is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

Hey, I created gatsby-plugin-source-eventbrite, not realized yours existed.

I created mine to work using the Eventbrite JavaScript SDK and pulling organizers. I noticed you are pulling organization events, but I may be able to fit that into my solution since it uses the Search API.

I would love to combine efforts on this and make it really robust. Let me know what I can do to bring these two projects closer together.

There have been updates to the gatsby monorepo:

• • The dependency gatsby-plugin-sharp was updated from 2.0.19 to 2.0.20.

• The peerDependency gatsby was updated from 2.0.118 to 2.0.119.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

This monorepo update includes releases of one or more dependencies which all belong to the gatsby group definition.

gatsby is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

The devDependency prettier was updated from 1.15.0 to 1.15.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

prettier is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

The dependency gatsby-plugin-sharp was updated from 2.0.10 to 2.0.11.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

gatsby-plugin-sharp is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

There have been updates to the gatsby monorepo:

• • The dependency gatsby-plugin-sharp was updated from 2.0.26 to 2.0.27.

• The dependency gatsby-source-filesystem was updated from 2.0.23 to 2.0.24.
• The peerDependency gatsby was updated from 2.1.29 to 2.1.30.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

This monorepo update includes releases of one or more dependencies which all belong to the gatsby group definition.

gatsby is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

On line 16 of gatsby-node.js the plugin is combining the default entries of ['events', 'venues'] with user specified values at the project root's gatsby-config.js.

My API requests were working fine via the browser and looking into more detailed error messages from the promise caught error within fetch.js it would seem venues is not supported:

{
        "status_code": 403,
        "error_description": "You are not allowed to request the venues of this user.",
        "error": "NOT_AUTHORIZED"
} 

Removing venues from the list does allow gatsby to compile but due to the fact that venues aren't fetched, no nodes are built because all events need to be linked to an associated venue via the linkEventWithVenue func within createNodeRelations.js.

If i use an access token that results in 401 or 403 errors, the plugin will loop infinitely.

Looks like the fetch.js loop has no provision for breaking out of the loop during a catch

There have been updates to the gatsby monorepo:

• • The dependency gatsby-plugin-sharp was updated from 2.0.28 to 2.0.29.

• The dependency gatsby-source-filesystem was updated from 2.0.26 to 2.0.27.
• The peerDependency gatsby was updated from 2.1.33 to 2.1.34.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

This monorepo update includes releases of one or more dependencies which all belong to the gatsby group definition.

gatsby is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴