-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
WIP: Get extension working in vscode.dev #124
Conversation
src/lib/validation.js
Outdated
@@ -40,7 +39,7 @@ const isFileInWorkspace = (error) => { | |||
filePath = filePath + '.module'; | |||
} | |||
|
|||
return fs.existsSync(path.resolve(dirToActiveFile, filePath)); | |||
return vscode.workspace.fs.stat(path.resolve(dirToActiveFile, filePath)); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Roughly how to address fs
, however this extension relies on cli-lib
which uses fs
directly
Just posting an update here on the progress: Most of the functionality is here to allow the extension to work in the web version of VS Code and removes its reliance on the HS CLI-LIB as well. However, because the extension operates in a WebWorker, requests that are made to the HS API fail because they do not have CORS enabled. Discussing a path forward internally. |
Adds a new webpack config targeting browsers and fallbacks to handle most deps
Known issues:
@hubspot/cli-lib
and uses node'sfs
module so we'll need to find an alternative method of loading a configFixes: #123