Support for wpgraphql woocommerce

[LiamHillier]

Currently receiving errors while trying to use the woocommerce graphql plugin. Assuming this is related to the known issues you posted about. If so ignore this.

` gatsby-source-wordpress ingest WPGraphQL schema

<--- Last few GCs --->

[4088:0000010F2047D7A0] 59447 ms: Scavenge 1354.0 (1435.0) -> 1338.9 (1437.0) MB, 2.4 / 0.0 ms (average mu = 0.265, current mu = 0.219) allocation failure [4088:0000010F2047D7A0] 59457 ms: Scavenge 1354.4 (1437.0) -> 1339.3 (1439.5) MB, 2.4 / 0.0 ms (average mu = 0.265, current mu = 0.219) allocation failure [4088:0000010F2047D7A0] 59466 ms: Scavenge 1354.8 (1439.5) -> 1339.8 (1441.5) MB, 2.8 / 0.0 ms (average mu = 0.265, current mu = 0.219) allocation failure

<--- JS stacktrace --->

==== JS stack trace =========================================

0: ExitFrame [pc: 0000024A87EDC5C1]

Security context: 0x0375a6e1e6e9 <JSObject> 1: /* anonymous / [000002C1395C5149] [C:\Users\Liam\Desktop\wordpress-v4\node_modules@rematch\core\dist\cjs\rematch.js:~196] [pc=0000024A8817E1C3](this=0x00fd4ed26cc1 <Object map = 000002F3A6CDBF91>) 2: / anonymous /(aka / anonymous */) [000002C1395C4621] [C:\Users\Liam\Desktop\wordpress-v4\node_modules\gatsby-source-wordpress-experimental\ste...

FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory 1: 00007FF6FDB2DD8A v8::internal::GCIdleTimeHandler::GCIdleTimeHandler+4506 2: 00007FF6FDB08886 node::MakeCallback+4534 3: 00007FF6FDB09200 node_module_register+2032 4: 00007FF6FDE230DE v8::internal::FatalProcessOutOfMemory+846 5: 00007FF6FDE2300F v8::internal::FatalProcessOutOfMemory+639 6: 00007FF6FE009804 v8::internal::Heap::MaxHeapGrowingFactor+9620 7: 00007FF6FE0007E6 v8::internal::ScavengeJob::operator=+24550 8: 00007FF6FDFFEE3C v8::internal::ScavengeJob::operator=+17980 9: 00007FF6FE007B87 v8::internal::Heap::MaxHeapGrowingFactor+2327 10: 00007FF6FE007C06 v8::internal::Heap::MaxHeapGrowingFactor+2454 11: 00007FF6FE131EA7 v8::internal::Factory::NewFillerObject+55 12: 00007FF6FE1AF096 v8::internal::operator<<+73494 13: 0000024A87EDC5C1`

[TylerBarnes]

🤔 huh, that looks new to me actually. Maybe it's building too big of a gql query and runs out of memory. Are you able to share a URL I can point the source plugin at to try it out?

[TylerBarnes]

You could also try lowering the schema.queryDepth plugin option for the source plugin. It might be that it's making a really massive query due to this being set to 15 levels.

[LiamHillier]

🤔 huh, that looks new to me actually. Maybe it's building too big of a gql query and runs out of memory. Are you able to share a URL I can point the source plugin at to try it out?

Sure, try https://dev.hillzy.com.au/graphql

[TylerBarnes]

Thanks for the report and the link! This is actually 2 separate bugs :p good news is they aren't hard to solve

[TylerBarnes]

This is fixed as of a few versions ago! :) I can't guarantee that everything in wp-graphql-woocommerce will work properly, but once we've moved from alpha to beta we'll be bugfixing and ensuring compatibility with it. So sourcing it works now, but I'm not totally sure wether or not cache invalidation and other features are working properly for it.

[LiamHillier]

@TylerBarnes Awesome thank you.

Can confirm that there are still some issues, e.g. Child categories are empty and attributes are buggy. Will be awaiting the beta :)