What is your technical stack and what are you building?

• Frontend: HTML, CSS, JavaScript, React, Redux, EJS
• Backend: NodeJS, MongoDB
• CI/CD: GitHub Actions, CircleCI

I am mostly building websites and web apps at the moment.

Comments

[Shane McGowan]

Frontend: Angular (9 I think), CSS
Backend: ASP.NET Core 3 Web API, MSSQL Server
CI/CD: AWS Code Pipelines / Code Deploy

Working on a website with the intention of hooking up android and iOS Apps later on.

ASP.NET Core is very nice to work with, great step forward for Microsoft

[Arnaud Cortisse]

I've just released a blog post explaining the tech stack I used to build DoNotSkip.

Ckeck it out :)

[Andrew Baisden]

Good read it's amazing how many tools, techs, platforms and services us developers require to make production ready applications.

[Marco Colli]

Or you could do yourself a favor and use only 1: Ruby on Rails. I really recommend it for your next project :)

[Pacharapol Withayasakpunt]

Combination of my laziness and maintainability. My current stack is

• Nuxt.js / Buefy
• Node.js / Fastify (for API validation +/- OpenAPI)
• MongoDB (via Typegoose) + Embedded LokiJS
• Firebase Auth
• Plausible analytics
• Docker / Google Cloud Run
• Desktop -- Electron

They all may change at any time, though.

Building a highly customizable quiz app, with embedded dictionaries, that can work on mobile, and sync to desktop.

[Andrew Baisden]

How are you finding Electron I am yet to create anything with it but I hear that it is quite easy to learn?

[Pacharapol Withayasakpunt]

Actually, it just appears to be the most reliable way to embed both Node.js and Chromium web browser for the client.

The best way (and most secure way) to use it, is via inter-process communication (ipcMain / ipcRender), which can also be done in pure Node.js (i.e. no Electron, is also true threading). However, I still prefer to do it the web server way.

Actually, if you don't really need the Node.js part, or you want different backends, there are many alternatives, e.g. Neutralino.js, zserge/webview. There is no guarantee that Chromium / CEF will work the way you wanted, though.

[AstroWorldMerch]

Frontend: Angular (9 I think), CSS
Backend: ASP.NET Core 3 Web API, MSSQL Server
CI/CD: AWS Code Pipelines / Code Deploy
Actually, it just appears to be the most reliable way to embed both Node.js and Chromium web browser for the client.
working on the website:
astroworldmerch.shop/

[Keff]

Back End:

• Api Platform
• NodeJS
• MongoDB
• MariaDB

Front End:

• Angular
• React
• Material Design
• Bootstrap (although I tend to not use it very often)

CI/CD:

• Github Actions (previously, CircleCI and TravisCI, and even before that we used Jenkins)

[starpebble]

Frontend: JavaScript/CSS/HTML/React/Materials
Backend: Amplify, Lambda, NodeJS, S3, DynamoDB, GraphQL
CI/CD: Amplify Hosted Pipeline, 'aws amplify cli', CloudFormation

This stack runs on serverless computing.

[Reaper]

Mongo
Ftrouter (Node.js)
Preact

Something that I can't reveal right now but if it gains enough traction after the MVP release, I might quit my job.

[Ben Halpern]

Frontend: Vanilla JS + Preact + Custom utility class CSS
Backend: Ruby on Rails
CI/CD: TravisCI (Up for changing this)

Building Forem

[Nguyen Trong Duc Luong]

i'm following the MERN stack, trying to make a meme generator website

[Andreas Møller]

Frontend: React, NextJS, styled-components, react-query.
Backend: Hasura, postgres.

I'm building a No-code editor for building interactive frontend apps.