-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add script to generate a built-in extension pack #56
Add script to generate a built-in extension pack #56
Conversation
c61cfde
to
4c7a1dc
Compare
I see this is quickly documented in the README: |
58e51dd
to
7b51ded
Compare
The new script 'create-extension-pack.js' can be executed directly after a project build (i.e. yarn) as long as the extensions associated with the build are already available in the registry. When the extensions are not yet available in the registry the script 'package-vsix.js' needs to be executed as a previous step. The result will be an extension package in .vsix format installed under the 'dist' folder (which is then used as the source for the existing publishing step). This extension package will include a reference to all extensions resolved during the build step. Fixes: eclipse-theia#40 Signed-off-by: Alvaro Sanchez-Leon <alvaro.sanchez-leon@ericsson.com>
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.
LGTM - once we merge we will obtain a pack for the latest @next version o fvscode. We can use the publish branch to program a build for older versions.
Thanks @alvsan09 for this contribution, Merging. |
The new script 'create-extension-pack.js' can be executed directly
after a project build (i.e. yarn) as long as the extensions
associated with the build are already available in the registry.
When the extensions are not yet available in the registry the script
'package-vsix.js' needs to be executed as a previous step.
The result will be an extension package in .vsix format installed
under the 'dist' folder (which is then used as the source for the
existing publishing step).
This extension package will include a reference to all extensions
resolved during the build step.
Fixes: #40
Signed-off-by: Alvaro Sanchez-Leon alvaro.sanchez-leon@ericsson.com