Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error: Failed to install dependencies with yarn. #416

Closed
i-bsd opened this issue May 10, 2019 · 10 comments
Closed

Error: Failed to install dependencies with yarn. #416

i-bsd opened this issue May 10, 2019 · 10 comments

Comments

@i-bsd
Copy link

i-bsd commented May 10, 2019

Description

❯ Clone https://github.com/gridsome/gridsome-starter-default.git 0.44s
❯ Update project package.json 0s
❯ Install dependencies
  • Building fresh packages (4 of 4)
Error: Failed to install dependencies with yarn. Please enter goo directory and install dependencies with yarn or npm manually. Then run gridsome develop to start local development.

    Exit code 1
    at ChildProcess.<anonymous> (/usr/home/user/.npm-packages/lib/node_modules/@gridsome/cli/lib/commands/create.js:100:17)
    at ChildProcess.emit (events.js:196:13)
    at maybeClose (internal/child_process.js:1011:16)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:268:5)

Steps to reproduce

gridsome create goo

Simply trying to create a new site project after a fresh install.

Expected result

It should create a new project without error.

Actual result

See above.

Environment


Libs:
- gridsome version: 0.0.9
- @gridsome/cli version: 0.0.9

Browser:
- [ ] Chrome (desktop) version XX
- [ ] Chrome (Android) version XX
- [ ] Chrome (iOS) version XX
- [X ] Firefox version 66.0.5
- [ ] Safari (desktop) version XX
- [ ] Safari (iOS) version XX
- [ ] IE version XX
- [ ] Edge version XX
 
For Tooling issues:
- Node version: 12.2.0
- Platform:  FreeBSD 12.0-RELEASE-p3

@hjvedvik
Copy link
Member

Change the gridsome version in package.json from 0.5.0 to 0.6.0 to make it work in Node.js 12.

@i-bsd
Copy link
Author

i-bsd commented May 10, 2019

Worked, thanks.

Is it always going to be necessary to manually change this in package.json?

@hjvedvik
Copy link
Member

No, we will update the version in the starters pretty soon :)

@i-bsd
Copy link
Author

i-bsd commented May 10, 2019

Default starter works. Other starters are causing other errors like this when running 'gridsome develop':

Gridsome v0.6.0

Initializing plugins...
Initialize - 1.06s
TypeError: Cannot read property 'tags' of undefined
    at FilesystemSource.createNodeRefs (/usr/home/user/Work/gridsome/my-project/node_modules/@gridsome/source-filesystem/index.js:71:36)
    at /usr/home/user/Work/gridsome/my-project/node_modules/@gridsome/source-filesystem/index.js:63:12
    at async Promise.all (index 0)
    at async FilesystemSource.createNodes (/usr/home/user/Work/gridsome/my-project/node_modules/@gridsome/source-filesystem/index.js:59:5)
    at async /usr/home/user/Work/gridsome/my-project/node_modules/@gridsome/source-filesystem/index.js:27:7
    at async Events.dispatch (/usr/home/user/Work/gridsome/my-project/node_modules/gridsome/lib/app/Events.js:24:11)
    at async App.loadSources (/usr/home/user/Work/gridsome/my-project/node_modules/gridsome/lib/app/App.js:144:5)
    at async App.bootstrap (/usr/home/user/Work/gridsome/my-project/node_modules/gridsome/lib/app/App.js:58:7)
    at async module.exports (/usr/home/user/Work/gridsome/my-project/node_modules/gridsome/lib/app/index.js:10:3)
    at async module.exports (/usr/home/user/Work/gridsome/my-project/node_modules/gridsome/lib/develop.js:10:15)

@hjvedvik
Copy link
Member

I think that error should have been fixed in @gridsome/source-filesystem@0.4.1.

@i-bsd
Copy link
Author

i-bsd commented May 10, 2019

Now I'm getting:

ERROR  Failed to compile with 3 errors
 error  in ./src/templates/Tag.vue?vue&type=custom&index=0&blockType=page-query

Module build failed (from ./node_modules/gridsome/lib/plugins/vue-components/lib/loaders/page-query.js):
Error: Cannot query field "coverImage" on type "Post". Did you mean "cover_image"?

@hjvedvik
Copy link
Member

Yes, that is one of the breaking changes in 0.6. Fields keep their original name. I think @tomtev will update the blog starter tomorrow :)

@i-bsd
Copy link
Author

i-bsd commented May 10, 2019

Ok. Well at least it's good to know there's nothing wrong with my setup.

I'll wait for the updates. Thanks!

@ghost
Copy link

ghost commented Sep 9, 2020

i have this problem. but i cant solve it. how can I?

@ghost
Copy link

ghost commented Sep 9, 2020

how can

i have this problem. but i cant solve it. how can i?

i solved it.
i used yarn instead npm.:))

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants