npm library for cards generation

[marcalexiei]

• Follow-up to Upstream a Stable Library API for the Action github-readme-stats-action#1

Creating an npm organization

If we decide to publish a package for rendering cards, I suggest creating an npm organization so that all related packages can live under a shared scope (e.g. @github-stats).
This would simplify ownership, improve discoverability, and support future expansion.

cards package

As an initial step, we could introduce a cards package that exports a render function for each supported card:

import { renderStatsCard, renderPinCard } from '@github-stats/cards';

The repository already contains both backend and frontend directories. Given the likelihood of additional packages,
it may be beneficial to convert the repository into a monorepo to better structure and isolate individual modules.

To keep this issue focused, I will open a separate discussion around adopting a monorepo.
This issue can remain scoped to the API design of the potential npm package(s).

[martin-mfg]

I have created https://www.npmjs.com/org/stats-organization .

@rickstaa's idea about the package structure was this:

Restructure the repo into npm packages, for example:

• @grs/core — core logic
• @grs/cards — official cards

This would allow others to create and publish their own cards independently.

Does this make sense for you?

[marcalexiei]

Sounds good to me!
Having a @grs/core package exposing base functions that can generate cards should help others to create and publish their own cards independently but relying on a common API.

I would suggest starting working on this once #17 is completed.