Skip to content

Several changes to the vscode extension build and release pipeline #64306

Closed
alan-agius4 wants to merge 4 commits into
angular:mainfrom
alan-agius4:vscode-release-and-srcs
Closed

Several changes to the vscode extension build and release pipeline #64306
alan-agius4 wants to merge 4 commits into
angular:mainfrom
alan-agius4:vscode-release-and-srcs

Conversation

@alan-agius4

@alan-agius4 alan-agius4 commented Oct 9, 2025

Copy link
Copy Markdown
Contributor

build: migrate to in-repo ts_project with strict deps

This commit migrates the vscode-ng-language-service to use the in-repo ts_project macro, which has strict dependency checking enabled. This improves build-time dependency validation and helps ensure that all dependencies are explicitly declared.

As part of this change, redundant tsconfig.json files have been removed in favor of a centralized configuration, and jasmine_test rules have been updated to the standard macro. A minor code adjustment in server/src/session.ts was also made to improve error handling.


build: add @angular/language-server to framework release output

This change updates the build configuration to include the
@angular/language-server package in the standard framework release
output.

By integrating it into the release train, we ensure that it is versioned and published consistently with the rest of the Angular framework.


build: use @angular/language-service from source

This commit updates the VSCode Angular Language Service extension to use the @angular/language-service package built from source within the workspace, rather than a version downloaded from npm.

This change simplifies development and testing by ensuring the extension always uses the latest code from the local repository. The Bazel build configuration, VSCode launch settings, and e2e tests have been updated to reflect this change.


build: remove unneeded language-service dependency

The @angular/language-service package was not needed for integration tests or benchmarks. Removing this dependency simplifies the build configuration.

@angular-robot angular-robot Bot added the area: build & ci Related the build and CI infrastructure of the project label Oct 9, 2025
@ngbot ngbot Bot added this to the Backlog milestone Oct 9, 2025
@alan-agius4 alan-agius4 changed the title Vscode release and srcs Several changes to the vscode extension build and release pipeline Oct 9, 2025
@alan-agius4 alan-agius4 force-pushed the vscode-release-and-srcs branch from b299e58 to 69085f7 Compare October 9, 2025 08:04
@alan-agius4 alan-agius4 added the target: major This PR is targeted for the next major release label Oct 9, 2025
@alan-agius4 alan-agius4 added the action: review The PR is still awaiting reviews from at least one requested reviewer label Oct 9, 2025
@alan-agius4 alan-agius4 marked this pull request as ready for review October 9, 2025 08:20
@alan-agius4 alan-agius4 force-pushed the vscode-release-and-srcs branch 10 times, most recently from 0e5e091 to 744b1a4 Compare October 9, 2025 10:09
const queryPackagesCmd =
`${bazelCmd} query --output=label "filter(':npm_package$', ` +
`attr('tags', '\\[.*${releaseTargetTag}.*\\]', //packages/...))"`;
`attr('tags', '\\[.*${releaseTargetTag}.*\\]', //packages/... + //vscode-ng-language-service/...))"`;

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe the whole package should have gone into packages/misc 😄

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Idk, maybe @josephperrott / @atscott can pitch in on that?

I can certainly do a follow-up to move it

@devversion devversion Oct 9, 2025

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍 for sure something we can follow-up on (if we even want to do something)

The `@angular/language-service` package was not needed for integration tests or benchmarks. Removing this dependency simplifies the build configuration.
This commit updates the VSCode Angular Language Service extension to use the `@angular/language-service` package built from source within the workspace, rather than a version downloaded from npm.

This change simplifies development and testing by ensuring the extension always uses the latest code from the local repository. The Bazel build configuration, VSCode launch settings, and e2e tests have been updated to reflect this change.
This change updates the build configuration to include the
@angular/language-server package in the standard framework release
output.

By integrating it into the release train, we ensure that it is versioned and published consistently with the rest of the Angular framework.
This commit migrates the vscode-ng-language-service to use the in-repo `ts_project` macro, which has strict dependency checking enabled. This improves build-time dependency validation and helps ensure that all dependencies are explicitly declared.

As part of this change, redundant `tsconfig.json` files have been removed in favor of a centralized configuration, and `jasmine_test` rules have been updated to the standard macro. A minor code adjustment in `server/src/session.ts` was also made to improve error handling.
@alan-agius4 alan-agius4 force-pushed the vscode-release-and-srcs branch from 744b1a4 to b99c52e Compare October 9, 2025 14:04
@alan-agius4 alan-agius4 removed the request for review from josephperrott October 9, 2025 15:36
@alan-agius4 alan-agius4 added action: merge The PR is ready for merge by the caretaker and removed action: review The PR is still awaiting reviews from at least one requested reviewer labels Oct 9, 2025
@alan-agius4 alan-agius4 added action: merge The PR is ready for merge by the caretaker and removed action: merge The PR is ready for merge by the caretaker labels Oct 9, 2025
@AndrewKushnir

Copy link
Copy Markdown
Contributor

This PR was merged into the repository. The changes were merged into the following branches:

AndrewKushnir pushed a commit that referenced this pull request Oct 9, 2025
This commit updates the VSCode Angular Language Service extension to use the `@angular/language-service` package built from source within the workspace, rather than a version downloaded from npm.

This change simplifies development and testing by ensuring the extension always uses the latest code from the local repository. The Bazel build configuration, VSCode launch settings, and e2e tests have been updated to reflect this change.

PR Close #64306
AndrewKushnir pushed a commit that referenced this pull request Oct 9, 2025
This change updates the build configuration to include the
@angular/language-server package in the standard framework release
output.

By integrating it into the release train, we ensure that it is versioned and published consistently with the rest of the Angular framework.

PR Close #64306
AndrewKushnir pushed a commit that referenced this pull request Oct 9, 2025
This commit migrates the vscode-ng-language-service to use the in-repo `ts_project` macro, which has strict dependency checking enabled. This improves build-time dependency validation and helps ensure that all dependencies are explicitly declared.

As part of this change, redundant `tsconfig.json` files have been removed in favor of a centralized configuration, and `jasmine_test` rules have been updated to the standard macro. A minor code adjustment in `server/src/session.ts` was also made to improve error handling.

PR Close #64306
@alan-agius4 alan-agius4 deleted the vscode-release-and-srcs branch October 9, 2025 17:01
@angular-automatic-lock-bot

Copy link
Copy Markdown

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot Bot locked and limited conversation to collaborators Nov 9, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

action: merge The PR is ready for merge by the caretaker area: build & ci Related the build and CI infrastructure of the project target: major This PR is targeted for the next major release

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants