posit-dev / posit-dev/connect-extensions

Add an Express.js example to the Connect Gallery

Open
#374 0 comments 0 reactions 1 assignee View on GitHub

@amylin1249 is already working on this.

Since Jun 29, 2026.

Dominant language
R
Stars
10
Forks
8
Avg merge
5d 18h
Merged PRs (30d)
1

Description

Add a Node.js content example to the Gallery: a small Express.js app demonstrating how to deploy Node.js content to Connect.

Depends on Connect Gallery support for Node.js requirements, shipping in Connect 2026.06, and on this repo's pipeline support for Node.js content (#373).

Work

  • Create extensions/express-example/ as simple content: an Express app with a package.json and a manifest.json.
  • package.json declares "engines": { "node": ">=22" }, the floor for the latest Express. This is what Connect uses to select a Node installation at build and run time, and what the release automation publishes as the Gallery requirement.
  • The manifest needs the standard extension section (name, title, description, homepage, category: "example", tags, minimumConnectVersion).
  • Set minimumConnectVersion to 2026.06.0, the release shipping Node.js general availability and Gallery support for Node.js requirements. This is what keeps older Connect UIs, which ignore the unknown nodejs key, from offering a doomed install.
  • Add tags (likely nodejs, javascript, express) to extensions.json; new tags need review per the contributing guide.
  • Add a README.md for the Gallery homepage link.
  • Register the path filter in .github/workflows/extensions.yml (simple-extension-changes).

Release timing

Keep version: "0.0.0" (no release) until Connect 2026.06 ships with Gallery support for Node.js requirements. Node.js content support is generally available in the same release.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.