Skip to content
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

Merged
merged 1 commit into from
May 11, 2021

Conversation

alvsan09
Copy link
Contributor

@alvsan09 alvsan09 commented Mar 18, 2021

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

src/create-extension-pack.js Outdated Show resolved Hide resolved
src/create-extension-pack.js Outdated Show resolved Hide resolved
src/create-extension-pack.js Outdated Show resolved Hide resolved
src/create-extension-pack.js Outdated Show resolved Hide resolved
src/create-extension-pack.js Show resolved Hide resolved
@marcdumais-work
Copy link
Contributor

src/create-extension-pack.js Outdated Show resolved Hide resolved
src/create-extension-pack.js Outdated Show resolved Hide resolved
src/create-extension-pack.js Outdated Show resolved Hide resolved
src/create-extension-pack.js Outdated Show resolved Hide resolved
@alvsan09 alvsan09 force-pushed the create-ext-pack branch 3 times, most recently from 58e51dd to 7b51ded Compare May 6, 2021 20:00
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>
Copy link
Contributor

@marcdumais-work marcdumais-work left a 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.

@marcdumais-work
Copy link
Contributor

Thanks @alvsan09 for this contribution, Merging.

@marcdumais-work marcdumais-work merged commit af9cfeb into eclipse-theia:master May 11, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

List all vscode built-ins
4 participants