You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
there is inconsistency in the node versions between Studio and the fixture project
That's strange. They're both using the exact same version of Redwood, so I wonder why you'd get that. If you could provide some reproduction steps that'd be great 🙏
I started fresh a second time. The first thing I did was:
~> nvm use
Found '/home/chris/WebstormProjects/studio/.nvmrc' with version <lts/*>
Now using node v20.11.0 (npm v10.2.4)
~> yarn install
yarn install v1.22.5
[1/5] Validating package.json...
error @11.1.1: The engine "node" is incompatible with this module. Expected version "=18.x". Got "20.11.0"
error Found incompatible module.
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
This happens because of the node engine setting in package.json:
After I remove that setting the yarn install command works.
Next, following the README I run:
~>cd __fixtures__/test-project && touch yarn.lock && yarn
yarn install v1.22.5
[1/5] Validating package.json...
[2/5] Resolving packages...
error "./../../packaged.tgz": Tarball is not in network and can not be located in cache (["/home/chris/WebstormProjects/studio/packaged.tgz","/home/chris/.cache/yarn/v6/.tmp/9f801d5d45273e9bb70f92bce1a9899d/.yarn-tarball.tgz"])
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
This error comes from the resolution in the test project's package.json and I never quite figured out a way to satisfy it:
This also sort of affects the packaging command (I tried to run to see if it would resolve the resolution issue):
~> yarn studio:package
yarn run v1.22.5
$ node ./tasks/package.mjs
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Studio: Package for Development
This script will build and package up studio.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
✔ Matching RW versions!
✔ Project built successfully!
✔ Packaged directory cleared!
✔ API files copied!
✔ Web files copied!
✔ DB files copied!
✔ Misc files copied!
✔ Set dependencies!
✔ Archive created!
⠴ Running yarn...[1/5] Validating package.json...
[2/5] Resolving packages...
error "./../../packaged.tgz": Tarball is not in network and can not be located in cache (["/home/chris/WebstormProjects/studio/packaged.tgz","/home/chris/.cache/yarn/v6/.tmp/9f801d5d45273e9bb70f92bce1a9899d/.yarn-tarball.tgz"])
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
I'm able to run RW_STUDIO_USER_PROJECT_PATH=./__fixtures__/test-project yarn rw dev fine and was able to test the changes I was working on well enough, I just couldn't do anything else inside the test project because of the above issues.
The text was updated successfully, but these errors were encountered:
This is follow up from redwoodjs/redwood/issues/9702 --
From @Tobbe:
I started fresh a second time. The first thing I did was:
This happens because of the node engine setting in
package.json
:studio/package.json
Lines 24 to 27 in af9588c
After I remove that setting the
yarn install
command works.Next, following the README I run:
This error comes from the resolution in the test project's
package.json
and I never quite figured out a way to satisfy it:studio/__fixtures__/test-project/package.json
Lines 24 to 26 in af9588c
This also sort of affects the packaging command (I tried to run to see if it would resolve the resolution issue):
I'm able to run
RW_STUDIO_USER_PROJECT_PATH=./__fixtures__/test-project yarn rw dev
fine and was able to test the changes I was working on well enough, I just couldn't do anything else inside the test project because of the above issues.The text was updated successfully, but these errors were encountered: