search

tinacms / gatsby-starter-tinacms

Gatsby starter for creating a blog with TinaCMS
MIT License
93 stars 14 forks source link

Gatsby develop fails directly after cloning with gatsby new #4

Closed sebastiannoell closed 4 years ago

sebastiannoell commented 4 years ago

Hey there 👋

Just freshly cloned the starter repo with these steps: https://tinacms.org/docs/gatsby/quickstart

I tried both commands gatsby develop and also npm run develop and both fail as I get serveral errors like

Generating SSR bundle failed
Can't import the named export '...' from non EcmaScript module (only default export is available)

Here's my logfile:

gatsby-develop.log

Gatsby info:

  System:
    OS: macOS 10.15.1
    CPU: (8) x64 Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz
    Shell: 5.7.1 - /bin/zsh
  Binaries:
    Node: 10.16.1 - /usr/local/bin/node
    npm: 6.13.1 - /usr/local/bin/npm
  Languages:
    Python: 2.7.17 - /usr/local/bin/python
  Browsers:
    Chrome: 78.0.3904.97
    Safari: 13.0.3
  npmPackages:
    gatsby: ^2.15.36 => 2.15.36
    gatsby-image: ^2.2.27 => 2.2.27
    gatsby-plugin-feed: ^2.3.16 => 2.3.16
    gatsby-plugin-google-analytics: ^2.1.21 => 2.1.21
    gatsby-plugin-manifest: ^2.2.21 => 2.2.21
    gatsby-plugin-offline: ^3.0.14 => 3.0.14
    gatsby-plugin-react-helmet: ^3.1.11 => 3.1.11
    gatsby-plugin-sharp: ^2.2.29 => 2.2.29
    gatsby-plugin-tinacms: ^0.1.7 => 0.1.14
    gatsby-plugin-typography: ^2.3.12 => 2.3.12
    gatsby-remark-copy-linked-files: ^2.1.26 => 2.1.26
    gatsby-remark-images: ^3.1.26 => 3.1.26
    gatsby-remark-prismjs: ^3.3.18 => 3.3.18
    gatsby-remark-responsive-iframe: ^2.2.23 => 2.2.23
    gatsby-remark-smartypants: ^2.1.12 => 2.1.12
    gatsby-source-filesystem: ^2.1.31 => 2.1.31
    gatsby-tinacms-git: ^0.2.4 => 0.2.12
    gatsby-tinacms-remark: ^0.3.4 => 0.3.6
    gatsby-transformer-remark: ^2.6.28 => 2.6.28
    gatsby-transformer-sharp: ^2.2.21 => 2.2.21
  npmGlobalPackages:
    gatsby-cli: 2.8.12
    gatsby: 2.14.3
spbyrne commented 4 years ago

Hey @sebastiannoell thanks for reporting this! I'm troubleshooting now; I see the same errors coming up on my end.

kendallstrautman commented 4 years ago

Could be related 👉 https://github.com/ProseMirror/prosemirror/issues/1003

I'm also getting a similar error on a nextjs setup after upgrading Tina.

[ error ] ../node_modules/prosemirror-commands/dist/index.mjs
[0] Can't import the named export 'AllSelection' from non EcmaScript module (only default export is available)
kendallstrautman commented 4 years ago

Assuming this specific error is resolved with the latest prosemirror update.