Skip to content

Deprecation signals: warn when a project with server-side JavaScript or TypeScript is published - #8071

Merged
ThuF merged 2 commits into
masterfrom
issue-8049-deprecation-signals
Oct 22, 2026
Merged

ThuF merged 2 commits into
masterfrom
issue-8049-deprecation-signals

Conversation

@ThuF

@ThuF ThuF commented Oct 22, 2026

Copy link
Copy Markdown
Contributor

Overview

Developers who publish server-side JavaScript or TypeScript now see the deprecation where they work - in the log, the Problems view and an IDE banner - with a link to the migration guide, and an instance without the JavaScript engine reports what it skips instead of dropping it silently.

Fixes: #8049.

template: `<div class="fd-margin--tiny" ng-if="!dismissed && projects.length">
<bk-message-strip state="warning" glyph="sap-icon--message-warning" on-dismiss="dismiss()">
Server-side JavaScript and TypeScript are deprecated and will be removed in 16.0. Used by: {{ projects.join(', ') }}.
See the Problems view and the <a class="fd-link" href="{{ guide }}" target="_blank" rel="noopener noreferrer">migration guide</a>.
try {
parsed = JsonParser.parseString(content(extension));
} catch (JsonParseException e) {
LOGGER.debug("Extension [{}] is not JSON, so it registers no module to count", extension.getPath(), e);
@ThuF
ThuF merged commit 6d46c4a into master Oct 22, 2026
16 checks passed
@ThuF
ThuF deleted the issue-8049-deprecation-signals branch October 22, 2026 17:57
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.

Deprecation signals: warn when a project with server-side JavaScript or TypeScript is published

2 participants