Skip to content

Conversation

@OSfrog
Copy link
Contributor

@OSfrog OSfrog commented Jan 8, 2026

Hey, I just made a Pull Request!

Added alpha exports for the new Backstage frontend system:

  • techInsightsPlugin: Main plugin for the new frontend system
  • techInsightsApi: API extension using ApiBlueprint
  • techInsightsScorecardPage: Page extension at /tech-insights
  • entityTechInsightsScorecardContent: Entity content tab
  • entityTechInsightsScorecardCard: Entity overview card

Usage:

import techInsightsPlugin from '@backstage-community/plugin-tech-insights/alpha';

const app = createApp({
  features: [techInsightsPlugin],
});

✔️ Checklist

  • A changeset describing the change and affected packages. (more info)
  • Added or updated documentation
  • Tests for new functionality and regression tests for bug fixes
  • Screenshots attached (for UI changes)
  • All your commits have a Signed-off-by line in the message. (more info)

@OSfrog OSfrog requested review from a team, Xantier and punkle as code owners January 8, 2026 08:33
@OSfrog OSfrog requested review from vinzscam and removed request for a team January 8, 2026 08:33
@backstage-service backstage-service added the workspace/tech-insights Used to tag tech-insights workspace issues and pull requests label Jan 8, 2026
@backstage-goalie
Copy link
Contributor

backstage-goalie bot commented Jan 8, 2026

Changed Packages

Package Name Package Path Changeset Bump Current Version
@backstage-community/plugin-tech-insights workspaces/tech-insights/plugins/tech-insights minor v0.7.0

@OSfrog OSfrog force-pushed the feat/tech-insights-new-frontend-system branch 5 times, most recently from 83ff50c to f746dc2 Compare January 8, 2026 09:10
@OSfrog
Copy link
Contributor Author

OSfrog commented Jan 8, 2026

Hi!

The Node 24.x CI failure appears to be a pre-existing infrastructure issue with better-sqlite3 not compiling on Node 24.x, unrelated to the changes in this PR:

gyp ERR! build error 
gyp ERR! stack Error: `make` failed with exit code: 2
...
/home/runner/work/community-plugins/community-plugins/workspaces/tech-insights/node_modules/@backstage/backend-defaults/node_modules/better-sqlite3

The Node 22.x CI step passes all checks (tsc, lint, tests, api-reports).

I noticed this was fixed in the announcements workspace via #6799 by updating better-sqlite3 from v9 to v12. The tech-insights workspace has the same issue:

 "better-sqlite3": "^9.0.0"  # packages/backend/package.json

Should I include the better-sqlite3 upgrade in this PR, or should that be a separate PR?

Copy link
Contributor

@awanlin awanlin left a comment

Choose a reason for hiding this comment

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

Hi @OSfrog, Tech Insights is currently built against version 1.39.0 of Backstage, we made the New Frontend System adoption ready in 1.42.0 and this included several API changes. Even if this were to be merged you would find there's issues with it being used by other Adopters along with the New Frontend System. I would pause work on this PR and get Tech Insights version bumped to 1.46.x at which point you can rebase this PR and fix any of the breaking API changes.

@OSfrog
Copy link
Contributor Author

OSfrog commented Jan 9, 2026

@awanlin Thanks for the quick response. Shall I go ahead and create a separate PR for the version bump?

@awanlin
Copy link
Contributor

awanlin commented Jan 9, 2026

I've generated the version bump PR for you here: #6826. You'll want to review the changelogs for each version it's going through - 1.39.0 to 1.46.2 - and apply any manual changes to the PR @OSfrog.

@OSfrog OSfrog force-pushed the feat/tech-insights-new-frontend-system branch 2 times, most recently from eff418d to 4b13a60 Compare January 9, 2026 14:55
@awanlin
Copy link
Contributor

awanlin commented Jan 10, 2026

@OSfrog please rebase, the version bump for Tech Insights to 1.46.x has been merged, keep in mind you'll likely run into breaking changes around the New Frontend System after that.

@OSfrog OSfrog force-pushed the feat/tech-insights-new-frontend-system branch from 4b13a60 to f28f801 Compare January 12, 2026 07:27
@OSfrog
Copy link
Contributor Author

OSfrog commented Jan 12, 2026

Thanks @awanlin! I've rebased on main and addressed the breaking changes from the 1.46.x upgrade:

New Frontend System changes addressed:

  • Updated defaultPathpath and defaultTitletitle in EntityContentBlueprint and PageBlueprint (breaking change from v1.42.0)
  • Using the current ApiBlueprint with defineParams callback style
  • Using compatWrapper from @backstage/core-compat-api to wrap legacy components

Backend changes:

  • Updated test expectation for httpRouter.use call count (4 → 3)

All checks pass locally (tsc, lint, tests). Ready for review!

Copy link
Member

@vinzscam vinzscam left a comment

Choose a reason for hiding this comment

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

Nice!

@OSfrog OSfrog force-pushed the feat/tech-insights-new-frontend-system branch 3 times, most recently from ae3b322 to 619985a Compare January 13, 2026 12:56
@OSfrog
Copy link
Contributor Author

OSfrog commented Jan 13, 2026

@vinzscam requested changes are made, is there anything else needed to merge this? We are being blocked by this PR 🙇

*
* @alpha
*/
export const entityTechInsightsScorecardCard = EntityCardBlueprint.make({
Copy link
Member

Choose a reason for hiding this comment

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

Two things to consider, even as follow-ups:

  1. End users are likely going to want some customization over the component, so I see this being converted to a makeWithOverrides blueprint.
  2. Should we filter out any entity kinds by default? Right now this will appear on all entity kinds by default.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Good points! What do you think about filtering out Location and Domain entities? I think the rest are fine.

Copy link
Member

Choose a reason for hiding this comment

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

I still think these are good things to consider, but I'm now doubting doing it on this first release. I'm not fully understanding how consumers configure how and where this component appears in the new frontend system.

@OSfrog OSfrog force-pushed the feat/tech-insights-new-frontend-system branch from 619985a to 5889d5d Compare January 16, 2026 05:33
Added alpha exports for the new Backstage frontend system:
- techInsightsPlugin: Main plugin for the new frontend system
- techInsightsApi: API extension using ApiBlueprint
- techInsightsScorecardPage: Page extension at /tech-insights
- entityTechInsightsScorecardContent: Entity content tab
- entityTechInsightsScorecardCard: Entity overview card

Signed-off-by: Tommy Le <[email protected]>
@OSfrog OSfrog force-pushed the feat/tech-insights-new-frontend-system branch from 5889d5d to 5bfac5d Compare January 16, 2026 05:43
Copy link
Member

@kurtaking kurtaking left a comment

Choose a reason for hiding this comment

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

Noticed a few more things

*
* @alpha
*/
export const entityTechInsightsScorecardCard = EntityCardBlueprint.make({
Copy link
Member

Choose a reason for hiding this comment

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

I still think these are good things to consider, but I'm now doubting doing it on this first release. I'm not fully understanding how consumers configure how and where this component appears in the new frontend system.

Copy link
Member

@kurtaking kurtaking left a comment

Choose a reason for hiding this comment

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

I've tested installing locally with a new instance of Backstage on the new frontend system and think we are good to go with initial release here.

Thanks for the contribution!

@kurtaking kurtaking assigned kurtaking and OSfrog and unassigned kurtaking Jan 16, 2026
@kurtaking kurtaking requested a review from vinzscam January 16, 2026 17:51
@kurtaking
Copy link
Member

@vinzscam, this is still pending requested changes from you which have been addressed. Can we either dismiss your review or have you provide approval? Thanks!

@kurtaking kurtaking merged commit b5f45fd into backstage:main Jan 16, 2026
13 checks passed
@kurtaking
Copy link
Member

I've opened #6945 as a follow-up to add a nav item.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

workspace/tech-insights Used to tag tech-insights workspace issues and pull requests

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants