Project won't re-package
I have projects A and B
When I
pnpm dev --verbose
in B, it works fine
When I pnpm dev --verbose
in A, it's stuck on
Both are using a forked version of Plasmo 0.61.2
The weird thing is that project A had previously worked fine, whereas project B did not work as I wanted it to work31 Replies
are both of them running at the same time? ;d
Even if they don't, project A is still stuck
try killing all nodes process and see if it run, on a side note - what was the last diff that lead to it not running?
what was the last diff that lead to it not running?You mean on the Plasmo side? I tried to add and them removed a
console.log
On project A, nothing was added
Just tried killing node.exe
, still facing the same issue@louis After investigating, it seems like project A is stuck on https://github.com/PlasmoHQ/plasmo/blob/340f38d200963ea9337a552c1cb4a9d904b7e313/cli/plasmo/src/commands/dev.ts#L55
No error; it simply pauses on
bundler.watch
GitHub
plasmo/dev.ts at 340f38d200963ea9337a552c1cb4a9d904b7e313 ยท PlasmoH...
๐งฉ The Browser Extension Framework. Contribute to PlasmoHQ/plasmo development by creating an account on GitHub.
It doesn't run anything after that line?
Nope, specifically in project A
In project B it runs as usual
try remove the .plasmo directory
and rerun
Didn't work
It did proceed to
but that's about it
if you put a console.log at the bottom of the dev fx
does it log anything at all?
If I log at 101, it does log
yeah so it means it run past that stuff
so what's happening now seems like an issue within whatever is running the framework
how's the .plasmo directory compared to B?
Project B
Project A
YouTube Like-Dislike Shortcut used to work, I have no idea why it stopped compiling properly
and no build was produced for the like-dislike?
hmmmmm
can you check the content of the plasmo.manifest file
and see if there's anything weird between them
also note the version at the beginning when dev runs
hmm beside no name it seems to be fine :d.....
also it went to the step of generating the manifest and the whole build directory
so I suspect the issue lies downstream somewhere ?....
If you really want, I can temporarily push it to GitHub
yee
that'd be great, I can try tinkering with it
You know what, I will push it to GitHub as a private repo and grant you access
aight
Pending invite
๐
@louis Do you have a projection when you're going to inspect the code to see what went wrong?
It seems like the issue was about having
svelte-preprocess
and sass
as dev deps rather than depsayo just got out - so does it work if you move them to deps?
generally for extension it doesn't matter much anyway, since the bundler will take whatever is available
Seems like so
I haven't gotten a chance to look at your project yet mb xd
been on call since last night and also fixing up some weird polyfill issue so I've been running on like 3-4hr of crashin xd
lol
Anyway, my whole goal of getting YouTube Like-Dislike Shortcut to work is to compare the broken Steam ID Finder (
<Content> was not found
or something), see why it happens and work it out such that the Steam ID Finder code will just work
If I could actually place breakpoints in WebStorm, it could potentially be faster, but I guess I have to rely on console.logsyeee xd