denoland / denoland/docs

Track and display introduction version for Deno Runtime APIs

Open
#2,670 0 comments 0 reactions 0 assignees View on GitHub
enhancement help wanted
Dominant language
TypeScript
Stars
204
Forks
385
Avg merge
14h 49m
Merged PRs (30d)
7

Description

Add per-API version metadata and surface it in the docs as small chips. Examples how this could look like:

- "Added in vX.Y"

- "Stable since vX.Y"

- Deprecated in vX.Y

etc (basically something similar to what node already does).

P.S. I searched the issue tracker but couldn’t find an existing issue for this. apologies if I missed it and this is a duplicate

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by locating how the Deno Runtime API Reference is generated and where API metadata is defined. Determine how per-API introduction, stability, and deprecation versions should be represented, then render chips such as “Added in vX.Y” in the docs. Done means the relevant API pages display accurate version metadata consistently.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
documentation
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.