Open patrickgdl opened 1 month ago
Got it working with the installed Chrome in WSL2.
But it is a Turborepo and it only works when I am inside the extension folder and running npm run dev
, it doesn't work when I run turbo run dev --filter=@my-project/extension
. Throws the same TypeError [ERR_INVALID_ARG_TYPE]: The "paths[0]" argument must be of type string. Received null
.
Maybe is something related to Turborepo?
hi @patrickgdl thanks for reporting! the error you found is a regression also reported in https://github.com/extension-js/extension.js/issues/138. This will be patched in the next release which should happen in the next few days. I'll keep this ticket open for tracking and will let you know when fixed.
Issue with Running in WSL2 - Stuck on "compiled successfully"
Description: I'm encountering issues when running within a WSL2 instance. I'm seeking best practices, suggestions, or examples for handling such setups on command-line-based Linux environments.
Steps to Reproduce:
google-chrome
.Observed Behavior: Upon executing the command, I receive the following error:
This seems related to Chrome not being installed within WSL2.
Troubleshooting Steps Taken:
google-chrome
, which creates a separate instance of Chrome from Windows but functions correctly.Current Behavior: When running
extension dev
, the process gets stuck oncompiled successfully
without progressing further:Versions Tested:
Additional Information:
Any help or guidance on resolving this issue would be greatly appreciated!