open-index/open-npm huggingface dataset:
npm package: @madnesslabs/fireenjin-backend
Description: This is a back-end development stack that uses Firebase and GraphQL with the magic of TypeScript.
Author: Madness Labs
Latest version: 1.0.7

# FireEnjin Backend

This is a back-end development stack that uses Firebase and GraphQL with the magic of TypeScript.

# How to Install

1. git clone https://github.com/MadnessLabs/fireenjin-backend
2. npm install
3. Download Service Account JSON from Firebase Project Settings and put it as service-account.json in the root. (See GIF below.)
   ![LT6RvC27Qp](https://user-images.githubusercontent.com/4184680/66259522-8fba8180-e777-11e9-8e37-a7034c06ebd9.gif)

# How to Play

## build

Delete the dist folder and run TypeScript compiler to build project.

## build:firebase

Delete the dist folder, run TypeScript compiler, and generate Firebase Functions index with RESTful API.

## clean

Delete the dist folder.

## codegen

Generate typings and StencilJS components from models and queries.

## env

Copy files from env folder and overwrite specific files per environment.

## deploy:graphql

Deploy your GraphQL instance to Google Cloud.

## deploy:firebase

Deploy your triggers (Cloud Functions) to Firebase.

## lint

Run linting on TypeScript files.

## migrate

Run migrations that haven't already ran from src/migrations folder.

## release

Build a release of the backend, typings, and Stencil components.

## seed

Deploy seeds from src/seeds to firestore collections.

## seed:clone

Copy down data from firestore collections to src/seeds.

## serve

Serve the project via a local web server and watch for changes to reload.

## start

This is a alias for the serve command

## test

This will run tests via jest.

## test:watch

This will run a watcher on all your tests
npm package: @madnesslabs/fireenjin-components
Description: ![Built With Stencil](https://img.shields.io/badge/-Built%20With%20Stencil-16161d.svg?logo=data%3Aimage%2Fsvg%2Bxml%3Bbase64%2CPD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0idXRmLTgiPz4KPCEtLSBHZW5lcmF0b3I6IEFkb2JlIElsbHVzdHJhdG9yIDE5LjIuMSwgU1ZHIEV4cG9ydCBQbHVn
Latest version: 1.3.23

![Built With Stencil](https://img.shields.io/badge/-Built%20With%20Stencil-16161d.svg?logo=data%3Aimage%2Fsvg%2Bxml%3Bbase64%2CPD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0idXRmLTgiPz4KPCEtLSBHZW5lcmF0b3I6IEFkb2JlIElsbHVzdHJhdG9yIDE5LjIuMSwgU1ZHIEV4cG9ydCBQbHVnLUluIC4gU1ZHIFZlcnNpb246IDYuMDAgQnVpbGQgMCkgIC0tPgo8c3ZnIHZlcnNpb249IjEuMSIgaWQ9IkxheWVyXzEiIHhtbG5zPSJodHRwOi8vd3d3LnczLm9yZy8yMDAwL3N2ZyIgeG1sbnM6eGxpbms9Imh0dHA6Ly93d3cudzMub3JnLzE5OTkveGxpbmsiIHg9IjBweCIgeT0iMHB4IgoJIHZpZXdCb3g9IjAgMCA1MTIgNTEyIiBzdHlsZT0iZW5hYmxlLWJhY2tncm91bmQ6bmV3IDAgMCA1MTIgNTEyOyIgeG1sOnNwYWNlPSJwcmVzZXJ2ZSI%2BCjxzdHlsZSB0eXBlPSJ0ZXh0L2NzcyI%2BCgkuc3Qwe2ZpbGw6I0ZGRkZGRjt9Cjwvc3R5bGU%2BCjxwYXRoIGNsYXNzPSJzdDAiIGQ9Ik00MjQuNywzNzMuOWMwLDM3LjYtNTUuMSw2OC42LTkyLjcsNjguNkgxODAuNGMtMzcuOSwwLTkyLjctMzAuNy05Mi43LTY4LjZ2LTMuNmgzMzYuOVYzNzMuOXoiLz4KPHBhdGggY2xhc3M9InN0MCIgZD0iTTQyNC43LDI5Mi4xSDE4MC40Yy0zNy42LDAtOTIuNy0zMS05Mi43LTY4LjZ2LTMuNkgzMzJjMzcuNiwwLDkyLjcsMzEsOTIuNyw2OC42VjI5Mi4xeiIvPgo8cGF0aCBjbGFzcz0ic3QwIiBkPSJNNDI0LjcsMTQxLjdIODcuN3YtMy42YzAtMzcuNiw1NC44LTY4LjYsOTIuNy02OC42SDMzMmMzNy45LDAsOTIuNywzMC43LDkyLjcsNjguNlYxNDEuN3oiLz4KPC9zdmc%2BCg%3D%3D&colorA=16161d&style=flat-square)

# FireEnjin Components

## Overview

---

Our component development process uses [StencilJS](https://stenciljs.com) to avoid using any framework and to build out to standard compliant Web Components.  

## Release

---

The components release process is built around [Github Actions](https://github.com/features/actions) and will build a new release using [Semantic Release](https://semantic-release.gitbook.io/semantic-release/) when commits are made to the master branch. This can be configured in the /.github/workflows/release.yml.

## Deploy

---

The components deploy process is built around [Github Actions](https://github.com/features/actions) and will deploy automatically to [Firebase Hosting](https://firebase.google.com/docs/hosting) when commits are made to the master branch. This can be configured in the /.github/workflows/deploy.yml.


## Special Thanks

---

Special thanks to dutscher for putting together a great example of using StencilJS with Storybook, which we used as the base for this project.
npm package: @madnesslabs/fireenjingraphql
Description: This is a back-end development stack that uses Firebase and GraphQL with the magic of TypeScript.
Author: Madness Labs
Latest version: 1.26.6

# FireEnjin GraphQL

This is a back-end development stack that uses Firebase and GraphQL with the magic of TypeScript.

# How to Install

1. git clone https://github.com/MadnessLabs/FireEnjinGraphQL
2. npm install
3. Download Service Account JSON from Firebase Project Settings and put it as service-account.json in the root. (See GIF below.)
   ![LT6RvC27Qp](https://user-images.githubusercontent.com/4184680/66259522-8fba8180-e777-11e9-8e37-a7034c06ebd9.gif)

# How to Play

## build

Delete the dist folder and run TypeScript compiler to build project.

## build:firebase

Delete the dist folder, run TypeScript compiler, and generate Firebase Functions index with RESTful API.

## clean

Delete the dist folder.

## codegen

Generate typings and StencilJS components from models and queries.

## env

Copy files from env folder and overwrite specific files per environment.

## deploy:graphql

Deploy your GraphQL instance to Google Cloud.

## deploy:firebase

Deploy your triggers (Cloud Functions) to Firebase.

## lint

Run linting on TypeScript files.

## migrate

Run migrations that haven't already ran from src/migrations folder.

## release

Build a release of the backend, typings, and Stencil components.

## seed

Deploy seeds from src/seeds to firestore collections.

## seed:clone

Copy down data from firestore collections to src/seeds.

## serve

Serve the project via a local web server and watch for changes to reload.

## start

This is a alias for the serve command

## test

This will run tests via jest.

## test:watch

This will run a watcher on all your tests

# Where to Next

Below is a link to a Notion note where we are actively working on fleshing out this full-stack structure to make building a project simpler. Any feedback is welcomed, please send us an email to info@MadnessLabs.net or find us on Twitter @MadnessLabs.

https://www.notion.so/madnesslabs/Project-Skeleton-fc1c44581c714be3abbe51df3fed48f1