Parallel dev servers

I need to both run plasmo dev --verbose and plasmo dev --verbose --target=firefox-mv3, but when I run the latter I get
πŸ”΅ INFO | Starting the extension development server...
🟑 1 | Starting dev server on localhost:52111, HMR on localhost:52112...
🟑 2 | Creating Manifest Factory...
🟑 3 | Loaded env from .env.local
🟑 4 | Loaded env from .env
🟑 5 | Ensure exists: C:\repositories\extensions\youtube-time-manager\.plasmo
🟑 6 | Busting large build cache, size: 1.81 GB
πŸ”΄ ERROR | EBUSY: resource busy or locked, unlink 'C:\repositories\extensions\youtube-time-manager\.plasmo\cache\parcel\data.mdb'
🟑 7 | Error: EBUSY: resource busy or locked, unlink 'C:\repositories\extensions\youtube-time-m anager\.plasmo\cache\parcel\data.mdb'
πŸ”΄ EXIT | πŸ‘‹ Good bye and have a great day!
πŸ”΅ INFO | Starting the extension development server...
🟑 1 | Starting dev server on localhost:52111, HMR on localhost:52112...
🟑 2 | Creating Manifest Factory...
🟑 3 | Loaded env from .env.local
🟑 4 | Loaded env from .env
🟑 5 | Ensure exists: C:\repositories\extensions\youtube-time-manager\.plasmo
🟑 6 | Busting large build cache, size: 1.81 GB
πŸ”΄ ERROR | EBUSY: resource busy or locked, unlink 'C:\repositories\extensions\youtube-time-manager\.plasmo\cache\parcel\data.mdb'
🟑 7 | Error: EBUSY: resource busy or locked, unlink 'C:\repositories\extensions\youtube-time-m anager\.plasmo\cache\parcel\data.mdb'
πŸ”΄ EXIT | πŸ‘‹ Good bye and have a great day!
5 Replies
avi12
avi12β€’5mo ago
@louis Possibly need to fix with a PR πŸ™ˆ
lab
labβ€’5mo ago
hmm interesting It looks like the cache was not busted entirely?..
avi12
avi12β€’5mo ago
Again, I need to run plasmo dev and plasmo dev --target=firefox-mv3 in parallel
lab
labβ€’5mo ago
ooh right that'd keep on trying to hit the same cache file... one solution is to spawn a new random cache for each plasmo dev lol maybe with a --parallel flag, it should set a random cache dir
avi12
avi12β€’5mo ago
Oki If you're curious, I need to launch multiple dev servers is to test cross browser data synchronization OK that's amazing Somehow, after automagically upgrading to 0.85.0 it got resolved without any additional flags