yarn rw dev not working

[PeterChen1997]

Version 1.0

After i scaffold a model, and the server get stucked. I kill the server and cannot restart again

I get nothing if i re run yarn rw dev

peterchen@MacBook-Pro mini-habits % yarn
➤ YN0000: ┌ Resolution step
➤ YN0002: │ @endemolshinegroup/cosmiconfig-typescript-loader@npm:3.0.2 [077a2] doesn't provide typescript (pe2a7f), requested by ts-node
➤ YN0002: │ @redwoodjs/api-server@npm:1.0.0 doesn't provide @babel/core (p23f02), requested by @babel/plugin-transform-runtime
➤ YN0002: │ @redwoodjs/cli@npm:1.0.0 doesn't provide react (pc03d1), requested by @redwoodjs/prerender
➤ YN0002: │ @redwoodjs/cli@npm:1.0.0 doesn't provide react-dom (p5c733), requested by @redwoodjs/prerender
➤ YN0002: │ @redwoodjs/core@npm:1.0.0 doesn't provide @babel/eslint-parser (pb856f), requested by @babel/eslint-plugin
➤ YN0002: │ @redwoodjs/core@npm:1.0.0 doesn't provide eslint (p2e746), requested by @babel/eslint-plugin
➤ YN0002: │ @redwoodjs/eslint-config@npm:1.0.0 doesn't provide babel-plugin-module-resolver (pa04e9), requested by eslint-import-resolver-babel-module
➤ YN0002: │ @redwoodjs/graphql-server@npm:1.0.0 doesn't provide @envelop/core (p13263), requested by @envelop/depth-limit
➤ YN0002: │ @redwoodjs/graphql-server@npm:1.0.0 doesn't provide @envelop/core (pabfeb), requested by @envelop/disable-introspection
➤ YN0002: │ @redwoodjs/graphql-server@npm:1.0.0 doesn't provide @envelop/core (p7ea2e), requested by @envelop/filter-operation-type
➤ YN0002: │ @redwoodjs/graphql-server@npm:1.0.0 doesn't provide @envelop/core (p1a19d), requested by @envelop/parser-cache
➤ YN0002: │ @redwoodjs/graphql-server@npm:1.0.0 doesn't provide @envelop/core (pcfa08), requested by @envelop/validation-cache
➤ YN0002: │ @redwoodjs/internal@npm:1.0.0 doesn't provide @babel/core (paa80d), requested by @babel/plugin-transform-typescript
➤ YN0002: │ @redwoodjs/internal@npm:1.0.0 doesn't provide @babel/core (p9bde4), requested by @babel/register
➤ YN0002: │ @redwoodjs/internal@npm:1.0.0 doesn't provide @babel/core (p41023), requested by babel-plugin-graphql-tag
➤ YN0002: │ @redwoodjs/internal@npm:1.0.0 doesn't provide @babel/core (pb0d3b), requested by babel-plugin-polyfill-corejs3
➤ YN0060: │ @redwoodjs/internal@npm:1.0.0 provides graphql (p0e2f7) with version 16.3.0, which doesn't satisfy what @graphql-codegen/typescript-operations and some of its descendants request
➤ YN0002: │ @redwoodjs/internal@npm:1.0.0 doesn't provide graphql-tag (p4a1c9), requested by @graphql-codegen/typescript-react-apollo
➤ YN0002: │ @redwoodjs/internal@npm:1.0.0 doesn't provide graphql-tag (pdea93), requested by babel-plugin-graphql-tag
➤ YN0002: │ @redwoodjs/prerender@npm:1.0.0 [95342] doesn't provide prop-types (pdf6a0), requested by @redwoodjs/web
➤ YN0002: │ @redwoodjs/router@npm:1.0.0 doesn't provide react (pec9eb), requested by @reach/skip-nav
➤ YN0002: │ @redwoodjs/router@npm:1.0.0 doesn't provide react-dom (pfc3ea), requested by @reach/skip-nav
➤ YN0002: │ @redwoodjs/testing@npm:1.0.0 doesn't provide @babel/core (p704cd), requested by babel-jest
➤ YN0002: │ @redwoodjs/testing@npm:1.0.0 doesn't provide @babel/core (p9c28b), requested by babel-plugin-inline-react-svg
➤ YN0002: │ @redwoodjs/testing@npm:1.0.0 doesn't provide @testing-library/dom (p47c52), requested by @testing-library/user-event
➤ YN0002: │ @redwoodjs/testing@npm:1.0.0 doesn't provide prop-types (pd68e9), requested by @redwoodjs/web
➤ YN0002: │ @redwoodjs/testing@npm:1.0.0 doesn't provide react (pc931c), requested by @redwoodjs/web
➤ YN0002: │ @redwoodjs/testing@npm:1.0.0 doesn't provide react (pd2096), requested by @storybook/builder-webpack5
➤ YN0002: │ @redwoodjs/testing@npm:1.0.0 doesn't provide react (p11a13), requested by @storybook/manager-webpack5
➤ YN0002: │ @redwoodjs/testing@npm:1.0.0 doesn't provide react (pb2f96), requested by @storybook/react
➤ YN0002: │ @redwoodjs/testing@npm:1.0.0 doesn't provide react (pe5a2f), requested by @testing-library/react
➤ YN0002: │ @redwoodjs/testing@npm:1.0.0 doesn't provide react-dom (pe4841), requested by @redwoodjs/web
➤ YN0002: │ @redwoodjs/testing@npm:1.0.0 doesn't provide react-dom (pfb387), requested by @storybook/builder-webpack5
➤ YN0002: │ @redwoodjs/testing@npm:1.0.0 doesn't provide react-dom (pacc79), requested by @storybook/manager-webpack5
➤ YN0002: │ @redwoodjs/testing@npm:1.0.0 doesn't provide react-dom (p4f653), requested by @storybook/react
➤ YN0002: │ @redwoodjs/testing@npm:1.0.0 doesn't provide react-dom (p43eca), requested by @testing-library/react
➤ YN0002: │ react-hot-toast@npm:2.2.0 [0bf7d] doesn't provide csstype (p5ecf4), requested by goober
➤ YN0002: │ react-hot-toast@npm:2.2.0 [290df] doesn't provide csstype (pd3124), requested by goober
➤ YN0002: │ react-hot-toast@npm:2.2.0 [83621] doesn't provide csstype (pbf39f), requested by goober
➤ YN0002: │ web@workspace:web doesn't provide graphql (pce9e6), requested by @redwoodjs/forms
➤ YN0000: │ Some peer dependencies are incorrectly met; run yarn explain peer-requirements <hash> for details, where <hash> is the six-letter p-prefixed code
➤ YN0000: └ Completed in 0s 313ms
➤ YN0000: ┌ Fetch step
➤ YN0000: └ Completed in 1s 465ms
➤ YN0000: ┌ Link step
➤ YN0000: └ Completed in 0s 626ms
➤ YN0000: Done with warnings in 2s 649ms
peterchen@MacBook-Pro mini-habits % yarn rw dev
peterchen@MacBook-Pro mini-habits % 

[Tobbe]

@PeterChen1997 That's the worst when you don't get any feedback at all on what's wrong 🙁

What's your output from yarn rw info?

[pvenable]

I got into a similar state the other day after a yarn rw upgrade. I was getting no output from yarn rw dev and my api tests were exiting early (though web tests were running normally).

I was unable to determine the cause, but in my case I was able to fix things by removing node_modules/ entirely and re-running yarn, and then everything worked as expected.

[PeterChen1997]

got it, i will run this command if i met it again

I fix it by restart my mac 😂

[jtoar]

@PeterChen1997 and @pvenable glad things are working, let us know if anything comes up again!

[PeterChen1997]

I met this problem again, after i upgrage to 1.3.0

I fix it by delete node_modules... I think it maybe a problem for other users

[jtoar]

@PeterChen1997 gotcha, I'll reopen for now. I still can't reproduce it, but maybe we can gather some more information. I'll try a few more things.

[PeterChen1997]

got it! Thx!

[jtoar]

I haven't been able to reproduce this yet, but we've added back a dedupe step to upgrades—that may help fix errors like this that (we think) are due to node_modules. Let us know if this shows up again when you upgrade after v1.3.2. There's no next release yet so that'd be impossible to test (unless you want to try out canary! yarn rw upgrade --tag canary), but for later.