kalwalt
commented
3 years ago Hi @taghp I will test It, haven't started a new project lately with It.
Open taghp opened 3 years ago
kalwalt
commented
3 years ago Hi @taghp I will test It, haven't started a new project lately with It.
kalwalt
commented
3 years ago I don't encounter this issue, see my log:
~/kalwalt-github/test> gatsby new mytest https://github.com/kalwalt/gatsby-starter-i18n-bulma
info Creating new site from git:
https://github.com/kalwalt/gatsby-starter-i18n-bulma.git
Clone in 'mytest' in corso...
remote: Enumerating objects: 180, done.
remote: Counting objects: 100% (180/180), done.
remote: Compressing objects: 100% (157/157), done.
remote: Total 180 (delta 30), reused 68 (delta 12), pack-reused 0
Ricezione degli oggetti: 100% (180/180), 3.64 MiB | 1.03 MiB/s, fatto.
success Created starter directory layout
info Installing packages...
info Preferred package manager set to "npm"
npm WARN deprecated gatsby-image@3.0.0: This package has been deprecated in favor of gatsby-plugin-image. The migration guide can be found here: https://www.gatsbyjs.com/docs/reference/release-notes/image-migration-guide/.
npm WARN deprecated core-js@2.6.12: 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 request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated @hapi/joi@15.1.1: Switch to 'npm install joi'
npm WARN deprecated har-validator@5.1.5: this library is no longer supported
npm WARN deprecated cheerio-select-tmp@0.1.1: Use cheerio-select instead
npm WARN deprecated @hapi/address@2.1.4: Moved to 'npm install @sideway/address'
npm WARN deprecated @hapi/hoek@8.5.1: This version has been deprecated and is no longer supported or maintained
npm WARN deprecated @hapi/bourne@1.3.2: This version has been deprecated and is no longer supported or maintained
npm WARN deprecated @hapi/topo@3.1.6: This version has been deprecated and is no longer supported or maintained
npm WARN deprecated core-js@1.2.7: 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 chokidar@2.1.8: Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies.
npm WARN deprecated urix@0.1.0: Please see https://github.com/lydell/urix#deprecated
npm WARN deprecated @types/vfile-message@2.0.0: This is a stub types definition. vfile-message provides its own type definitions, so you do not need this installed.
npm WARN deprecated fsevents@1.2.13: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
npm WARN deprecated resolve-url@0.2.1: https://github.com/lydell/resolve-url#deprecated
> sharp@0.27.2 install /home/walter/kalwalt-github/test/mytest/node_modules/sharp
> (node install/libvips && node install/dll-copy && prebuild-install) || (node-gyp rebuild && node install/dll-copy)
info sharp Using cached /home/walter/.npm/_libvips/libvips-8.10.5-linux-x64.tar.br
> core-js@2.6.12 postinstall /home/walter/kalwalt-github/test/mytest/node_modules/core-js
> node -e "try{require('./postinstall')}catch(e){}"
Thank you for using core-js ( https://github.com/zloirock/core-js ) for polyfilling JavaScript standard library!
The project needs your help! Please consider supporting of core-js on Open Collective or Patreon:
> https://opencollective.com/core-js
> https://www.patreon.com/zloirock
Also, the author of core-js ( https://github.com/zloirock ) is looking for a good job -)
> core-js-pure@3.9.1 postinstall /home/walter/kalwalt-github/test/mytest/node_modules/core-js-pure
> node -e "try{require('./postinstall')}catch(e){}"
> core-js@3.9.1 postinstall /home/walter/kalwalt-github/test/mytest/node_modules/gatsby/node_modules/core-js
> node -e "try{require('./postinstall')}catch(e){}"
> gatsby-telemetry@2.0.0 postinstall /home/walter/kalwalt-github/test/mytest/node_modules/gatsby-telemetry
> node src/postinstall.js || true
> mozjpeg@7.0.0 postinstall /home/walter/kalwalt-github/test/mytest/node_modules/mozjpeg
> node lib/install.js
✔ mozjpeg pre-build test passed successfully
> pngquant-bin@6.0.0 postinstall /home/walter/kalwalt-github/test/mytest/node_modules/pngquant-bin
> node lib/install.js
✔ pngquant pre-build test passed successfully
> gatsby-cli@3.0.0 postinstall /home/walter/kalwalt-github/test/mytest/node_modules/gatsby-cli
> node scripts/postinstall.js
> gatsby@3.0.4 postinstall /home/walter/kalwalt-github/test/mytest/node_modules/gatsby
> node scripts/postinstall.js
npm notice created a lockfile as package-lock.json. You should commit this file.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@~2.3.1 (node_modules/chokidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.3.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.2.7 (node_modules/webpack-dev-server/node_modules/chokidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.13: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN gatsby-plugin-react-leaflet@3.0.0 requires a peer of gatsby@^2.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN gatsby-plugin-remove-trailing-slashes@2.10.0 requires a peer of gatsby@^2.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN netlify-cms-app@2.14.29 requires a peer of react@^16.8.4 but none is installed. You must install peer dependencies yourself.
npm WARN netlify-cms-app@2.14.29 requires a peer of react-dom@^16.8.4 but none is installed. You must install peer dependencies yourself.
npm WARN react-images@1.1.7 requires a peer of react@^15.3.0 || ^16.2.0 but none is installed. You must install peer dependencies yourself.
npm WARN react-images@1.1.7 requires a peer of react-dom@^15.3.0 || ^16.2.0 but none is installed. You must install peer dependencies yourself.
npm WARN react-intl@4.7.6 requires a peer of react@^16.3.0 but none is installed. You must install peer dependencies yourself.
npm WARN react-photo-gallery@8.0.0 requires a peer of react@^16.8.0 but none is installed. You must install peer dependencies yourself.
npm WARN react-photo-gallery@8.0.0 requires a peer of react-dom@^16.8.0 but none is installed. You must install peer dependencies yourself.
npm WARN babel-preset-gatsby@1.0.0 requires a peer of core-js@^3.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN eslint-config-react-app@6.0.0 requires a peer of babel-eslint@^10.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN express-graphql@0.9.0 requires a peer of graphql@^14.4.1 but none is installed. You must install peer dependencies yourself.
npm WARN tsutils@3.21.0 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 ts-node@9.1.1 requires a peer of typescript@>=2.7 but none is installed. You must install peer dependencies yourself.
npm WARN @pieh/friendly-errors-webpack-plugin@1.7.0-chalk-2 requires a peer of webpack@^2.0.0 || ^3.0.0 || ^4.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN netlify-cms-backend-azure@1.1.2 requires a peer of react@^16.8.4 but none is installed. You must install peer dependencies yourself.
npm WARN netlify-cms-backend-bitbucket@2.12.8 requires a peer of react@^16.8.4 but none is installed. You must install peer dependencies yourself.
npm WARN netlify-cms-backend-git-gateway@2.11.11 requires a peer of react@^16.8.4 but none is installed. You must install peer dependencies yourself.
npm WARN netlify-cms-backend-github@2.11.9 requires a peer of react@^16.8.4 but none is installed. You must install peer dependencies yourself.
npm WARN netlify-cms-backend-test@2.10.7 requires a peer of react@^16.8.4 but none is installed. You must install peer dependencies yourself.
npm WARN netlify-cms-backend-gitlab@2.9.9 requires a peer of react@^16.8.4 but none is installed. You must install peer dependencies yourself.
npm WARN netlify-cms-core@2.38.7 requires a peer of react@^16.8.4 but none is installed. You must install peer dependencies yourself.
npm WARN netlify-cms-core@2.38.7 requires a peer of react-dom@^16.8.4 but none is installed. You must install peer dependencies yourself.
npm WARN netlify-cms-editor-component-image@2.6.7 requires a peer of react@^16.8.4 but none is installed. You must install peer dependencies yourself.
npm WARN netlify-cms-ui-default@2.12.1 requires a peer of react@^16.8.4 but none is installed. You must install peer dependencies yourself.
npm WARN netlify-cms-widget-boolean@2.3.6 requires a peer of react@^16.8.4 but none is installed. You must install peer dependencies yourself.
npm WARN netlify-cms-widget-code@1.2.7 requires a peer of codemirror@^5.46.0 but none is installed. You must install peer dependencies yourself.
npm WARN netlify-cms-widget-code@1.2.7 requires a peer of react@^16.8.4 but none is installed. You must install peer dependencies yourself.
npm WARN netlify-cms-widget-date@2.5.7 requires a peer of react@^16.8.4 but none is installed. You must install peer dependencies yourself.
npm WARN netlify-cms-widget-date@2.5.7 requires a peer of react-dom@^16.8.4 but none is installed. You must install peer dependencies yourself.
npm WARN netlify-cms-widget-colorstring@1.0.3 requires a peer of react@^16.8.4 but none is installed. You must install peer dependencies yourself.
npm WARN netlify-cms-widget-datetime@2.6.8 requires a peer of react@^16.8.4 but none is installed. You must install peer dependencies yourself.
npm WARN netlify-cms-widget-file@2.9.2 requires a peer of react@^16.8.4 but none is installed. You must install peer dependencies yourself.
npm WARN netlify-cms-widget-image@2.7.7 requires a peer of react@^16.8.4 but none is installed. You must install peer dependencies yourself.
npm WARN netlify-cms-widget-list@2.8.4 requires a peer of netlify-cms-lib-widgets@^1.6.1 but none is installed. You must install peer dependencies yourself.
npm WARN netlify-cms-widget-list@2.8.4 requires a peer of react@^16.8.4 but none is installed. You must install peer dependencies yourself.
npm WARN netlify-cms-widget-map@1.4.6 requires a peer of react@^16.8.4 but none is installed. You must install peer dependencies yourself.
npm WARN netlify-cms-widget-markdown@2.12.11 requires a peer of react@^16.8.4 but none is installed. You must install peer dependencies yourself.
npm WARN netlify-cms-widget-markdown@2.12.11 requires a peer of react-dom@^16.8.4 but none is installed. You must install peer dependencies yourself.
npm WARN netlify-cms-widget-number@2.4.7 requires a peer of react@^16.8.4 but none is installed. You must install peer dependencies yourself.
npm WARN netlify-cms-widget-object@2.6.2 requires a peer of react@^16.8.4 but none is installed. You must install peer dependencies yourself.
npm WARN netlify-cms-widget-relation@2.8.9 requires a peer of netlify-cms-lib-widgets@^1.6.1 but none is installed. You must install peer dependencies yourself.
npm WARN netlify-cms-widget-relation@2.8.9 requires a peer of react@^16.8.4 but none is installed. You must install peer dependencies yourself.
npm WARN netlify-cms-widget-select@2.7.4 requires a peer of netlify-cms-lib-widgets@^1.6.1 but none is installed. You must install peer dependencies yourself.
npm WARN netlify-cms-widget-select@2.7.4 requires a peer of react@^16.8.4 but none is installed. You must install peer dependencies yourself.
npm WARN netlify-cms-widget-string@2.2.10 requires a peer of react@^16.8.4 but none is installed. You must install peer dependencies yourself.
npm WARN netlify-cms-widget-text@2.3.6 requires a peer of react@^16.8.4 but none is installed. You must install peer dependencies yourself.
npm WARN react-scroll-sync@0.8.0 requires a peer of react@0.14.x || 15.x || 16.x but none is installed. You must install peer dependencies yourself.
npm WARN react-scroll-sync@0.8.0 requires a peer of react-dom@0.14.x || 15.x || 16.x but none is installed. You must install peer dependencies yourself.
npm WARN react-sortable-hoc@1.11.0 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 react-sortable-hoc@1.11.0 requires a peer of react-dom@^0.14.0 || ^15.0.0 || ^16.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN react-split-pane@0.1.92 requires a peer of react@^16.0.0-0 but none is installed. You must install peer dependencies yourself.
npm WARN react-split-pane@0.1.92 requires a peer of react-dom@^16.0.0-0 but none is installed. You must install peer dependencies yourself.
npm WARN react-waypoint@9.0.3 requires a peer of react@^15.3.0 || ^16.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN redux-notifications@4.0.1 requires a peer of react@^0.14.0 || ^15.0.0-0 || ^15.4.0-0 || ^16.0.0-0 but none is installed. You must install peer dependencies yourself.
npm WARN redux-notifications@4.0.1 requires a peer of react-dom@^0.14.0 || ^15.0.0-0 || ^15.4.0-0 || ^16.0.0-0 but none is installed. You must install peer dependencies yourself.
npm WARN react-redux@4.4.10 requires a peer of react@^0.14.0 || ^15.0.0-0 || ^15.4.0-0 || ^16.0.0-0 but none is installed. You must install peer dependencies yourself.
npm WARN react-redux@4.4.10 requires a peer of redux@^2.0.0 || ^3.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN react-transition-group@1.2.1 requires a peer of react@^15.0.0 || ^16.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN react-transition-group@1.2.1 requires a peer of react-dom@^15.0.0 || ^16.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN react-aria-menubutton@6.3.0 requires a peer of react@0.14.x || ^15.0.0 || ^16.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN react-aria-menubutton@6.3.0 requires a peer of react-dom@0.14.x || ^15.0.0 || ^16.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN create-react-context@0.3.0 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 react-codemirror2@7.2.1 requires a peer of react@>=15.5 <=16.x but none is installed. You must install peer dependencies yourself.
npm WARN react-codemirror2@7.2.1 requires a peer of codemirror@5.x but none is installed. You must install peer dependencies yourself.
npm WARN react-select@2.4.4 requires a peer of react@^15.3.0 || ^16.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN react-select@2.4.4 requires a peer of react-dom@^15.3.0 || ^16.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN react-input-autosize@2.2.2 requires a peer of react@^0.14.9 || ^15.3.0 || ^16.0.0-rc || ^16.0 but none is installed. You must install peer dependencies yourself.
npm WARN react-swipeable@5.5.1 requires a peer of react@^16.0.0-0 but none is installed. You must install peer dependencies yourself.
npm WARN html-react-parser@0.10.5 requires a peer of react@^0.14 || ^15 || ^16 but none is installed. You must install peer dependencies yourself.
npm WARN react-full-screen@0.2.5 requires a peer of react@^15.6 || ^16 but none is installed. You must install peer dependencies yourself.
npm WARN react-view-pager@0.6.0 requires a peer of react@0.14.x || ^15.0.0 || ^16.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN react-view-pager@0.6.0 requires a peer of react-dom@0.14.x || ^15.0.0 || ^16.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN react-motion@0.5.2 requires a peer of react@^0.14.9 || ^15.3.0 || ^16.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN react-addons-css-transition-group@15.6.2 requires a peer of react@^15.4.2 but none is installed. You must install peer dependencies yourself.
npm WARN gatsby-starter-i18n-bulma@1.1.5 No repository field.
added 2892 packages from 1785 contributors and audited 2899 packages in 138.577s
258 packages are looking for funding
run `npm fund` for details
found 1 low severity vulnerability
info Initialising git in mytest
suggerimento: Using 'master' as the name for the initial branch. This default branch name
suggerimento: is subject to change. To configure the initial branch name to use in all
suggerimento: of your new repositories, which will suppress this warning, call:
suggerimento:
suggerimento: git config --global init.defaultBranch <name>
suggerimento:
suggerimento: Names commonly chosen instead of 'master' are 'main', 'trunk' and
suggerimento: 'development'. The just-created branch can be renamed via this command:
suggerimento:
suggerimento: git branch -m <name>
info Create initial git commit in mytest
info
Your new Gatsby site has been successfully bootstrapped. Start developing it by
running:
cd mytest
gatsby develop
It could be that you are using an older version of nodejs and npm than mine consider that gatsby v. 3.0 require at least node v12.18.1. Can you post your node, npm and gatsby-cli version?
taghp
commented
3 years ago Thank you @kalwalt, I'll upgrade my nodejs and npm, then test it again.
kalwalt
commented
3 years ago @taghp You are welcome! Let us know if you solved!
taghp
commented
3 years ago using node 12.21.0, npm 6.14.11, and all is good. Thank you @kalwalt again.
kalwalt
commented
3 years ago Very good i think i need to add some infos in the Readme about node and npm version to be used.
JOduMonT
commented
3 years ago Hey; I think I have the same error here my version:
While resolving: gatsby-starter-i18n-bulma@v1.1.5
Found: gatsby@3.5.0
node_modules/gatsby
gatsby@"^3.0.0" from the root project
Could not resolve dependency:
peer gatsby@"^2.0.0" from gatsby-plugin-react-leaflet@3.0.0
node_modules/gatsby-plugin-react-leaflet
gatsby-plugin-react-leaflet@"^3.0.0" from the root project
Fix the upstream dependency conflict, or retry
this command with --force, or --legacy-peer-deps
to accept an incorrect (and potentially broken) dependency resolution.
Hey; I think I have the same error here my version:
- nodejs 14.16
- npm 7.12
- gatsby-cli 3.5
While resolving: gatsby-starter-i18n-bulma@v1.1.5 Found: gatsby@3.5.0 node_modules/gatsby gatsby@"^3.0.0" from the root project Could not resolve dependency: peer gatsby@"^2.0.0" from gatsby-plugin-react-leaflet@3.0.0 node_modules/gatsby-plugin-react-leaflet gatsby-plugin-react-leaflet@"^3.0.0" from the root project Fix the upstream dependency conflict, or retry this command with --force, or --legacy-peer-deps to accept an incorrect (and potentially broken) dependency resolution.
Sorry for the delay i haven't tested recently, maybe it is required to upgrade the gatsby version in the package.json?
JOduMonT
commented
3 years ago ok this morning I took the time to test again and it work
added 2766 packages from 2503 contributors and audited 2773 packages in 203.019s
279 packages are looking for funding run
npm fundfor detailsfound 15 vulnerabilities (1 low, 5 moderate, 9 high) info Initialising git in bulma
info Create initial git commit in bulma info Your new Gatsby site has been successfully bootstrapped. Start developing it by running:
cd bulma gatsby develop
noexec on my /home partition (/etc/fstab) but this is true for all SSGkalwalt
commented
3 years ago @JOduMonT Glad that you solved, strange that you need to:
I had to remove noexec on my /home partition (/etc/fstab) but this is true for all SSG
JOduMonT
commented
3 years ago @JOduMonT Glad that you solved, strange that you need to:
I had to remove noexec on my /home partition (/etc/fstab) but this is true for all SSG
not that much since the code is under /home if I move the code under /tmp or /srv it work
When trying gatsby new mytest https://github.com/kalwalt/gatsby-starter-i18n-bulma
I got this error:
npm ERR! code ERESOLVE npm ERR! ERESOLVE unable to resolve dependency tree npm ERR! npm ERR! While resolving: gatsby-starter-i18n-bulma@v1.1.5 npm ERR! Found: react@17.0.1 npm ERR! node_modules/react npm ERR! react@"^17.0.1" from the root project npm ERR! peer react@"^16.9.0 || ^17.0.0" from gatsby-plugin-netlify-cms@5.0.0 npm ERR! node_modules/gatsby-plugin-netlify-cms npm ERR! gatsby-plugin-netlify-cms@"^5.0.0" from the root project npm ERR! 2 more (gatsby, react-dom) npm ERR! npm ERR! Could not resolve dependency: npm ERR! peer react@"^16.8.4" from netlify-cms-app@2.14.29 npm ERR! node_modules/netlify-cms-app npm ERR! netlify-cms-app@"^2.14.26" from the root project npm ERR! peer netlify-cms-app@"^2.9.0" from gatsby-plugin-netlify-cms@5.0.0 npm ERR! node_modules/gatsby-plugin-netlify-cms npm ERR! gatsby-plugin-netlify-cms@"^5.0.0" from the root project npm ERR! npm ERR! Fix the upstream dependency conflict, or retry npm ERR! this command with --force, or --legacy-peer-deps npm ERR! to accept an incorrect (and potentially broken) dependency resolution.