facial-vote
Serverless-Boilerplate-Express-TypeScript
facial-vote | Serverless-Boilerplate-Express-TypeScript | |
---|---|---|
1 | 21 | |
3 | 533 | |
- | - | |
5.9 | 5.4 | |
8 months ago | about 1 month ago | |
TypeScript | TypeScript | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
facial-vote
-
Serverless Facial Recognition Voting Application Using AWS Services
# Clone this repository git clone https://github.com/chyke007/facial-vote.git # Go into the repository cd facial-vote
Serverless-Boilerplate-Express-TypeScript
-
My SaaS architecture (tech stack) on AWS as a solo developer
You can find more details in my open source boilerplate: https://github.com/ixartz/Serverless-Boilerplate-Express-TypeScript where I'm using TypeScript.
-
I made an Open Source Node.js Starter Template built with Serverless Framework + TypeScript + Prisma + MongoDB + Express.js + ESLint + Prettier + Jest + VSCode
You can check out the GitHub repo for more details at: Node.js Boilerplate with Serverless and Prisma
- My Open Source JS Backend Starter Kit built with Serverless Framework + TypeScript + Prisma + MongoDB + Express.js + ESLint + Prettier + Jest + VSCode
- I just add Prisma and In-memory MongoDB for local development into my Open Source Serverless Node.js Boilerplate built with TypeScript and Jest
- I just add Prisma and In-memory MongoDB for local development into my Serverless Node.js Boilerplate with TypeScript
- I made an Open Source Node.js Starter Template with Express.js + Serverless framework + TypeScript + Jest + ESLint + Prettier + Husky + Lint-Staged + Commitlint + Dotenv + VSCode (w/ Debugging)
-
Just updated my Node.js Serverless Backend Template by including Jest for testing and Commitlint for better commit message. Built with Express.js + TypeScript + Serverless Framework + ESLint + Prettier + Husky + Lint-Staged + VSCode + Dotenv
Here is the link to the Node.js Boilerplate code: https://github.com/ixartz/Serverless-Boilerplate-Express-TypeScript
- Test Node.js code with Jest directly with free VSCode extension: instant test feedback, real-time code coverage, problem inspector directly inside your editor. Writing tests is now much easier and enjoyable. Configuration in the comments.
-
I Updated my Open Source Serverless Starter Template with Serverless framework 3 + ExpressJS + TypeScript + ESLint (Airbnb config) + Prettier + Husky + Lint-Staged + VSCode (w/ Debugging)
You can checkout the Serverless Boilerplate Typescript GitHub repo.
-
Is Lambda Function URLs a good reason now to use Express.js or any other web framework in AWS Lambda
As you might know, AWS has recently announced AWS Lambda Function URLs. This is a new feature that allows you to deploy your lambda behind a HTTPS endpoint without API Gateway. So, no need to set up a API gateway with related cost associated to it or add complexity to your serverless architecture for a single lambda function. I'm the author of a Serverless Boilerplate Template that uses Express.js with AWS Lambda. Usually, I got a lot of questions on why I add Express.js to my boilerplate code. Indeed, adding Express.js with API Gateway is redundant and it's not necessary. It'll increase the deployed package size. Now with Lambda Function URLs, you don't need an API Gateway all the time. Without API gateway, all HTTP requests are sending to one lambda function. That means you need a Web framework to handle the request like Express.js. To be clear and avoid any confusion, API gateway is still a solution. But, based on your context and your needs, you can choose to use Lambda Function URLs and remove the API gateway. In the past, a lot of people were suggesting me to remove Express.js from my starter code. Now with Lambda Function, I'm not sure if it's a good idea to remove it from your boilerplate code. What is your thoughts on this?
What are some alternatives?
clickstream-analytics-on-aws - Build clickstream analytics on AWS for your mobile and web applications
typescript-monorepo-example - Typescript monorepo example
gradientify - ✨ Lambda to convert given image file into CSS gradients to use as skeleton loaders
serverless-graphql - Serverless GraphQL Examples for AWS AppSync and Apollo
weather-site - A workflow that hits a weather API and updates a website to show current conditions
ESLint - Find and fix problems in your JavaScript code.
aws-cloudformation-coverage-roadmap - The AWS CloudFormation Public Coverage Roadmap
youtube-playlist-length - Web app to calculate the duration of a YouTube playlist. Uses the YouTube data API v3
webiny-js - Open-source serverless enterprise CMS. Includes a headless CMS, page builder, form builder, and file manager. Easy to customize and expand. Deploys to AWS.
nx-serverless - 🚀 The Ultimate Monorepo Starter for Node.js Serverless Applications
jfa-whatsapp-chatbot - 🤖 With this node.js micro framework using Venom Bot under the hood, you can easily create a WhatsApp Chatbot. You will only need to edit your conversation flow in a single file.