Closed LangLangBart closed 8 months ago
@LangLangBart I solved here by adding npm run build
to the install-all-dependencies
task.
the reason this should be okay is that the gui in development now depends on npm run dev
instead of the actual built assets (index.js, index.css) (this means that we now have hot module reloading)
this means that we now have hot module reloading
Wunderbar.
Before submitting your bug report
Relevant environment info
Description
When a user clones the repository and follows the instructions from the contributing.md file, they will encounter a failure when executing the
install-all-dependencies
task.This issue can be traced back to the changes in the
prepackage.js
file with commit: 0419da7568670505706d1711859e714b00a8e2b5.The problem arises when the
npm run build
command does not execute, preventing the creation of thedist
folder, which in turn causes the script to fail.https://github.com/continuedev/continue/blob/76fe78a1a3c05b0d6dd5ed6d15575e20e797cfa6/extensions/vscode/scripts/prepackage.js#L56-L67
Failure message below:
Even if the
dist
folder exists but is empty, the script will fail later due to these lines:https://github.com/continuedev/continue/blob/76fe78a1a3c05b0d6dd5ed6d15575e20e797cfa6/extensions/vscode/scripts/prepackage.js#L87-L92
quick and dirty solution
Revert commit 0419da7, but only for the
prepackage.js
file.To reproduce
install-all-dependencies
Log output
No response