fortune-sheet icon indicating copy to clipboard operation
fortune-sheet copied to clipboard

Internal Error: fortune-sheet@workspace:.: This package doesn't seem to be present in your lockfile; run "yarn install" to update the lockfile

Open seleckis opened this issue 1 year ago • 6 comments

Hi, fresh install does not allow to run yarn dev.

To Reproduce Steps to reproduce the behavior:

  1. Fork repository
  2. git clone repository
  3. yarn install
  4. yarn dev
  5. See error:
yarn run v1.22.19
$ npx yarn storybook
Internal Error: fortune-sheet@workspace:.: This package doesn't seem to be present in your lockfile; run "yarn install" to update the lockfile

Expected behavior Working dev mode

Additional context I have tried to remove all lock files and reinstall, tried to add private: true to all package.json files. No luck

seleckis avatar Feb 19 '24 07:02 seleckis

This seems odd, what is your node version?

sanchit3008 avatar Mar 14 '24 05:03 sanchit3008

v18.12.1

seleckis avatar Mar 20 '24 09:03 seleckis

Thanks, I will check with this setting and let you know. I have been using it on 16.15.1 with yarn 1.22.19 for months now without problems. You can probably try it once with these settings too.

sanchit3008 avatar Mar 20 '24 10:03 sanchit3008

Sorry I am unable to reproduce this with yarn 1.22.19 / node 18.12 too. Just to be sure, you are running these commands in the root level of the repo right? This error would occur in case of a mismatch between the lockfile and the package.json.

sanchit3008 avatar Apr 04 '24 16:04 sanchit3008

This is fresh install to a separate folder which is not a part of another project. I'm running these commands in the root of this repository. Just tried again:

rm -rf node_modules yarn.lock
yarn
yarn dev

same result:

yarn run v1.22.19
$ npx yarn storybook
Internal Error: fortune-sheet@workspace:.: This package doesn't seem to be present in your lockfile; run "yarn install" to update the lockfile

seleckis avatar Apr 10 '24 06:04 seleckis

i am quite clueless about this at this stage to be honest, since i am unable to replicate this or be able to understand why this is happening and nobody else has been reporting this either. lets keep this issue open for now. apologies.

sanchit3008 avatar Apr 10 '24 20:04 sanchit3008