Closed dimitrisnl closed 2 years ago
Thanks for looking into this! I just approved the workflow runs so you can try to get CI passing. Once it’s green I’ll take closer look.
@andrewbranch Something weird is going on, the node 12 tests doesn't run at all (seems correct), and the node 14 has a strange error
14 quit because 12 failed—you can change all the workflow configs to test on 14/16 instead of 12/14.
Seems to be needing approval again, can you spare a moment @andrewbranch ?
some issues, the tests and prettier pass. Investigating.
@andrewbranch One more time
I would rather not enable skipLibCheck
since the repo contains hand-written .d.ts files. There’s no reason that eslint typings should be part of the compilation in the first place. Try adding "types": ["node", "jest"]
to the compiler options in tsconfig.json.
Updated @andrewbranch
You should be able to test this stuff locally by the way—CI isn’t doing anything fancy
Tests are not running properly locally for me. Assumed it would be a quick win to do it here, as I already have deployed these changes in my website and I have no issues.
Closing due to inactivity
As per the Gatsby migrations docs, we can't use
fs
anymore to import the GraphQL schema https://www.gatsbyjs.com/docs/reference/release-notes/migrating-source-plugin-from-v3-to-v4/#the-new-way-4old way
new way
We do pretty much the same, so:
createSchemaCustomization
hookThis should now allow us to us the plugin with GatsbyV4. Tested with
npm pack
and local import in my website.Fixes: https://github.com/andrewbranch/gatsby-remark-vscode/issues/174