gatsby-theme-mdx-deck not working

[mbifulco]

Hey there - I spent quite a bit of time this evening trying to get gatsby-theme-mdx-deck to work. I've run into a dead end in the most basic scenario I can think of - installing the theme on a fresh gatsby site:

1. create new gatsby site with gatsby new examplesite
2. cd examplesite
3. npm i gatsby-theme-mdx-deck

☝️ this step is not working currently - npm i takes a particularly long time to run, and ends with an error in the console:

node version: v12.16.2
npm version: 6.14.4

> npm i gatsby-theme-mdx-deck
npm WARN deprecated @hapi/[email protected]: joi is leaving the @hapi organization and moving back to 'joi' (https://github.com/sideway/joi/issues/2411)
npm WARN deprecated [email protected]: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
npm WARN deprecated [email protected]: core-js@<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js@3.
npm WARN deprecated @types/[email protected]: This is a stub types definition. vfile-message provides its own type definitions, so you do not need this installed.
npm WARN deprecated [email protected]: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated [email protected]: this library is no longer supported
npm WARN rm not removing /Users/mike/src/mdxdeck/node_modules/.bin/rimraf as it wasn't installed by /Users/mike/src/mdxdeck/node_modules/rimraf
npm WARN rm not removing /Users/mike/src/mdxdeck/node_modules/.bin/uuid as it wasn't installed by /Users/mike/src/mdxdeck/node_modules/uuid
npm WARN rm not removing /Users/mike/src/mdxdeck/node_modules/.bin/semver as it wasn't installed by /Users/mike/src/mdxdeck/node_modules/semver
npm WARN rm not removing /Users/mike/src/mdxdeck/node_modules/.bin/detect as it wasn't installed by /Users/mike/src/mdxdeck/node_modules/detect-port
npm WARN rm not removing /Users/mike/src/mdxdeck/node_modules/.bin/detect-port as it wasn't installed by /Users/mike/src/mdxdeck/node_modules/detect-port
npm WARN rm not removing /Users/mike/src/mdxdeck/node_modules/.bin/mkdirp as it wasn't installed by /Users/mike/src/mdxdeck/node_modules/mkdirp
npm WARN rm not removing /Users/mike/src/mdxdeck/node_modules/.bin/json5 as it wasn't installed by /Users/mike/src/mdxdeck/node_modules/json5
npm WARN rm not removing /Users/mike/src/mdxdeck/node_modules/.bin/mime as it wasn't installed by /Users/mike/src/mdxdeck/node_modules/mime
npm WARN notsup Unsupported engine for [email protected]: wanted: {"node":"<8.10.0"} (current: {"node":"12.16.2","npm":"6.14.4"})
npm WARN notsup Not compatible with your version of node/npm: [email protected]
npm WARN [email protected] requires a peer of gatsby@^2.4.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of gatsby@^2.4.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of gatsby@>2.0.15 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of gatsby@^2.12.1 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of react@^16.13.1 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of gatsby@^2.13.6 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of react@^16.8.6 but none is installed. You must install peer dependencies yourself.
npm WARN @reach/[email protected] requires a peer of [email protected] || 16.x || 16.4.0-alpha.0911da3 but none is installed. You must install peer dependencies yourself.
npm WARN @mdx-js/[email protected] requires a peer of react@^16.13.1 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of gatsby@^2.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of gatsby@^2.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN @emotion/[email protected] requires a peer of react@>=16.3.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of gatsby@>2.0.0-alpha but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of gatsby@^2.13.1 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of theme-ui@^0.2.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of react@^16.0.0-0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of react@>= 0.14.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of prop-types@^15.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of react@^0.14.0 || ^15.0.0 || ^16.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN @pmmmwh/[email protected] requires a peer of react-refresh@^0.8.2 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of gatsby@^2.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of react@^16.4.2 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of gatsby@^2.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of react@^16.4.2 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of react@^15.0.0 || ^16.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of typescript@>=2.8.0 || >= 3.2.0-dev || >= 3.3.0-dev || >= 3.4.0-dev || >= 3.5.0-dev || >= 3.6.0-dev || >= 3.6.0-beta || >= 3.7.0-dev || >= 3.7.0-beta but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of react@^16.8.2 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of react@>=16.8.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of react@^16.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of react@^16.12.0 but none is installed. You must install peer dependencies yourself.
npm WARN @mdx-js/[email protected] requires a peer of react@^16.13.1 but none is installed. You must install peer dependencies yourself.
npm WARN @emotion/[email protected] requires a peer of react@>=16.3.0 but none is installed. You must install peer dependencies yourself.
npm WARN @mdx-js/[email protected] requires a peer of react@^16.13.1 but none is installed. You must install peer dependencies yourself.
npm WARN @mdx-js/[email protected] requires a peer of react@^16.13.1 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of react@>=16.8.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of react@>=16.8.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of [email protected] but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of prop-types@^15.6.1 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of [email protected] but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of [email protected] but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of react@^16.8.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of react@^0.14.0 || ^15.0.0 || ^16.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of react@* but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of react@^16.13.1 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of react@>= 16.8.0 but none is installed. You must install peer dependencies yourself.
npm WARN @emotion/[email protected] requires a peer of react@>=16.3.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of acorn@^6.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN @reach/[email protected] requires a peer of react@^16.8.0 but none is installed. You must install peer dependencies yourself.
npm WARN @reach/[email protected] requires a peer of react@^16.8.0 but none is installed. You must install peer dependencies yourself.
npm WARN @reach/[email protected] requires a peer of react@^16.8.0 but none is installed. You must install peer dependencies yourself.
npm WARN @reach/[email protected] requires a peer of react@^16.8.0 but none is installed. You must install peer dependencies yourself.
npm WARN @reach/[email protected] requires a peer of react@^16.8.0 but none is installed. You must install peer dependencies yourself.
npm WARN @reach/[email protected] requires a peer of react@^16.8.0 but none is installed. You must install peer dependencies yourself.
npm WARN @reach/[email protected] requires a peer of react@^16.8.0 but none is installed. You must install peer dependencies yourself.
npm WARN @reach/[email protected] requires a peer of react@^16.8.0 but none is installed. You must install peer dependencies yourself.
npm WARN @reach/[email protected] requires a peer of react@^16.8.0 but none is installed. You must install peer dependencies yourself.
npm WARN @reach/[email protected] requires a peer of react@^16.8.0 but none is installed. You must install peer dependencies yourself.
npm WARN @reach/[email protected] requires a peer of react@^16.8.0 but none is installed. You must install peer dependencies yourself.
npm WARN @reach/[email protected] requires a peer of react@^16.8.0 but none is installed. You must install peer dependencies yourself.
npm WARN @reach/[email protected] requires a peer of react@^16.8.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of react@^16.8.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of react@^16.8.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of react@^16.8.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of react@^16.8.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of react@^15.3.0 || ^16.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of react@^16.8.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of react@^16.8.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of react@^16.3.0 but none is installed. You must install peer dependencies yourself.
npm WARN @theme-ui/[email protected] requires a peer of react@^16.8.0 but none is installed. You must install peer dependencies yourself.
npm WARN @theme-ui/[email protected] requires a peer of react@^16.11.0 but none is installed. You must install peer dependencies yourself.
npm WARN @theme-ui/[email protected] requires a peer of react@^16.11.0 but none is installed. You must install peer dependencies yourself.
npm WARN @theme-ui/[email protected] requires a peer of react@^16.11.0 but none is installed. You must install peer dependencies yourself.

npm ERR! code ENOENT
npm ERR! syscall rename
npm ERR! path /Users/mike/src/mdxdeck/node_modules/@ardatan/aggregate-error
npm ERR! dest /Users/mike/src/mdxdeck/node_modules/@ardatan/.aggregate-error.DELETE
npm ERR! errno -2
npm ERR! enoent ENOENT: no such file or directory, rename '/Users/mike/src/mdxdeck/node_modules/@ardatan/aggregate-error' -> '/Users/mike/src/mdxdeck/node_modules/@ardatan/.aggregate-error.DELETE'
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent 

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/mike/.npm/_logs/2020-09-01T01_15_25_287Z-debug.log
 ✘  ~/src/mdxdeck   master ●  

So - I'm trying to determine what's going on with the theme. Is it supported any longer? I'd love to help dig into what's going on here, but I'm at a bit of a loss for what else I can do to be helpful.