Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

New Project: Nitrogen (Shopify apps on Firebase)

Open Beginner friendly
  • Is something wrong?
#498 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
68/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Quiet
Tech stack
firebase, typescript
Domain
content, documentation

Research direction

Start with the submitted .opensource/project.json and read docs/configure-repo.md alongside config/additional_projects.json to verify the current project-registration workflow. Confirm the correct registry location and contributor guidance, then ensure the create-shopify-firebase-app entry can be processed by the site without relying on the obsolete additional-projects.json path.

Written by the indexing model from the issue text.

Description

GitHub link: https://github.com/mksd0398/nitrogen

What it is (2-3 sentences):
Nitrogen (npm: @mksd0398/nitrogen, formerly create-shopify-firebase-app). An MIT-licensed CLI that scaffolds an embedded Shopify app running entirely on Firebase — Hosting for the frontend, gen-2 Cloud Functions, one per API resource, for OAuth, the Admin API, webhooks and the storefront app proxy, and Firestore for session storage. One command takes you from nothing to a deployed, installable Shopify app, including creating and provisioning the Firebase project. It is positioned as the Firebase alternative to Shopify official Remix/React Router template, which assumes a Node server plus Postgres.

Why would Firebase developers be interested?
Shopify app development is a sizeable ecosystem whose official tooling assumes a long-running Node server and a relational database, so Firebase is not an obvious path and there is little material showing how to do it well. This project is a worked example of the serverless equivalent: session-token (JWT) verification on gen-2 Functions, Firestore as the OAuth session store with deny-all rules since access is admin-SDK only, HMAC verification for webhooks and app proxy, and Hosting rewrites mapping clean paths onto individual functions. It also makes a concrete cost argument for Firebase — the free tier covers a meaningful number of installed merchants before Blaze usage begins.

Have you added .opensource/project.json?
Yes — added at .opensource/project.json with platforms: ["Web"].

Note on the setup docs: docs/configure-repo.md currently instructs contributors to add their repo to additional-projects.json, but that file no longer exists in this repository — the live registry appears to be config/additional_projects.json. Happy to open a PR against whichever is correct if that is preferred over an issue.

Dominant language
TypeScript
Stars
127
Forks
49
No merged PRs in 30d

Getting set up

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.

More from firebase/firebaseopensource.com

All issues in firebase/firebaseopensource.com

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.