How do you debug a problem when yarn dev just exits?
I've got a bug where when I run yarn dev, it exists without printing anything useful:
(base) james@MacBook-Pro ~/workspace/ts/packages/cardstacker (ts)$ yarn dev
🟣 Plasmo v0.86.1
🔴 The Browser Extension Framework
🔵 INFO | Starting the extension development server...
🔵 INFO | Loaded environment variables from: []
(base) james@MacBook-Pro ~/workspace/ts/packages/cardstacker (ts)$
yarn build also reports no errors, but no files are produced:
(base) james@MacBook-Pro ~/workspace/ts/packages/cardstacker (ts)$ ls build/chrome-mv3-prod/
(base) james@MacBook-Pro ~/workspace/ts/packages/cardstacker (ts)$
Suggestions for how to tell plasmo I need something to tell me where the issue is? yarn dev --verbose is also useless as far as I can tell.
5 Replies
Have you tried
pnpm? The docs strongly suggset using it.
I find yarn to be a funny thing. Which version are you using? The Yarn 1.x version might have some issues.
The 1.x branch of Yarn has been in maintenance mode since early 2020. https://endoflife.date/yarn$ yarn --version
3.3.1
I've got too many pieces using yarn; switching to pnpm just for plasmo sounds like serious pain
Definitely no one should be using yarn 1, that's extremely ancient
I did finally get it working, but it was pretty much just hacking around; I had a dependency that seemed just fine, but removing it got rid of the problem.
heh you say no one shoudl be using Yarn 1, but I've seen it happen way too often.
@Sam has reached level 6. GG!
Yeah sorry I wasn't trying to tell you to switch to pnpm. Just following the docs and my experience.
What was the dependency? I'm kind of curious.