Getting Gatsby incremental build errors with Plasmic

Hi, we’re trying out Plasmic and are planning on using Gatsby since we’ve used that with our previous lander implementation. I was wondering if someone has gotten Gatsby Incremental builds to work with Plasmic? If I understood correctly, Gatsby doesn’t allow incremental builds if using http(s) requests in plugins.

These are the warnings I’m getting:

warning Unsafe builtin method was used, future builds will need to rebuild all pages
warning WebpackError: Unsafe builtin usage https.request: 
    at gatsby-starter-default/node_modules/node-fetch/lib/index.js:1468:1
    at gatsby-starter-default/node_modules/node-fetch/lib/index.js:1437:1
    at gatsby-starter-default/node_modules/@plasmicapp/loader-core/dist/loader-core.esm.js:849:27
    at gatsby-starter-default/node_modules/@plasmicapp/loader-core/dist/loader-core.esm.js:162:1
    at gatsby-starter-default/node_modules/@plasmicapp/loader-core/dist/loader-core.esm.js:379:1
    at gatsby-starter-default/node_modules/@plasmicapp/loader-core/dist/loader-core.esm.js:215:1
    at gatsby-starter-default/node_modules/@plasmicapp/loader-core/dist/loader-core.esm.js:5:1
    at gatsby-starter-default/node_modules/@plasmicapp/loader-core/dist/loader-core.esm.js:27:1
    at gatsby-starter-default/node_modules/@plasmicapp/loader-core/dist/loader-core.esm.js:34:1
    at gatsby-starter-default/node_modules/@plasmicapp/loader-core/dist/loader-core.esm.js:23:1
    at gatsby-starter-default/node_modules/@plasmicapp/loader-core/dist/loader-core.esm.js:886:1
    at gatsby-starter-default/node_modules/@plasmicapp/loader-core/dist/loader-core.esm.js:1160:1
    at gatsby-starter-default/node_modules/@plasmicapp/loader-core/dist/loader-core.esm.js:162:1
    at gatsby-starter-default/node_modules/@plasmicapp/loader-core/dist/loader-core.esm.js:379:1
  1466 |
  1467 | 		// send request
> 1468 | 		const req = send(options);
       | ^
  1469 | 		let reqTimeout;
  1470 |
  1471 | 		if (signal) {

Hi @spicy_lamprey! Unfortunately @plasmicapp/loader-gatsby does not currently support Gatsby incremental builds.

Alright, thanks for the info :slightly_smiling_face: Let’s see if it’s an issue for us or if we should switch to something like Next.js :+1: