react-starter-kit
sst
Our great sponsors
react-starter-kit | sst | |
---|---|---|
29 | 179 | |
22,502 | 19,951 | |
0.5% | 2.6% | |
5.7 | 9.9 | |
25 days ago | 10 days 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.
react-starter-kit
-
Major Update to React Starter Kit: Welcome Joy UI and Jotai!
Your Feedback Matters Your feedback is crucial for the continuous improvement of the React Starter Kit. Please try out the new version and share your thoughts and experiences. If you encounter any issues or have suggestions, feel free to open an issue on GitHub or join our community chat on Discord. We're excited to see the amazing applications you'll build with these new features! Happy coding! https://github.com/kriasoft/react-starter-kit
-
Ask HN: What is the best place to hire part time devs for small
Part-time can be a great fit for developers who use their own stack and stick to a consistent architecture across multiple projects. For instance, I personally begin each of my projects with the same template (https://github.com/kriasoft/react-starter-kit 23k). This approach reduces overhead when juggling multiple tasks, allowing me to seamlessly make changes in one place and effortlessly push and merge updates into various upstream repositories for different clients. Excited about this efficiency-boosting method? Check out my new blog post where I delve into the details: https://medium.com/@koistya/enabling-efficient-front-end-dev.... Good luck with your project!
-
Is NEXT.JS really that helpful versus react + express?
https://github.com/kriasoft/react-starter-kit (or, relay-starter-kit)
-
Is Chakra-UI still in use today? Or are there better libraries available now?
I like Joy UI library by Material UI team, while Material UI and Mantine, would be my 2nd and 3rd options respectively. Check out the list of UI libraries for React in this thread.
- Which Flux implementation should I use [for React]?
-
Building a SPA CRM application - Vite or Next.js?
I don't have much experience with Next.js. But since most of my projects are CRM-like applications, I find Vite works really great for that type of apps. I'm bootstrapping new projects with the React Starter Kit template (pre-configured with React, Material UI, Vite, Google Cloud Identity, and Cloudflare Workers).
-
Top 5 React Boilerplates to Know in 2023
4 React Starter Kit React Starter Kit The React library, which has 20.6k stars, served as the foundation for Kriasoft's isomorphic starter kit. Modern web development tools including Node.js, Express, GraphQL, Babel, PostCSS, Webpack, and Browsersync are used by React Starter Kit
- Which state management library is the best for React? (suggest any libraries that are not included in the poll)
-
Should Next be the default for React?
Vite in combination with Cloudflare Workers (for edge deployment) can be a solid default. See React Starter Kit as an example.
- What are some great advanced open source Reactjs projects to learn from?
sst
-
The 2024 Web Hosting Report
We see some great results from using these in conjunction with frameworks such as SST or Serverless, and also some real spaghetti from people who organically proliferate 100’s of functions over time and lose track of how they relate to each other or how to update them safely across time and service. Buyer beware!
-
Hono v4.0.0
> But if you have a sufficiently large enough API surface, doing one lambda per endpoint comes with a lot of pain as well. Packaging and deploying all of those artifacts can be very time consuming, especially if you have a naive approach that does a full rebuild/redeploy every time the pipeline runs.
Yeah, thankfully SST [0] does the heavy lifting for me. I've tried most of the solutions out there and SST was where I was the happiest. Right now I do 1 functions per endpoint. I structure my code like url paths mostly, 1 stack per final folder, so that the "users" folder maps to "/users/*" and inside I have get/getAll/create/update/delete files that map to GET X/id, GET X, POST X, POST X/id, DELETE/id. It works out well, it's easy to reason about, and deploys (a sizable a backend) in about 10min on GitHub Actions (which I'm going to swap out probably for something faster).
I agree with the secrets/permissions aspect and I like that it's stupid-simple for me to attach secrets/permissions at a low level if I want.
I use NodeJS and startup isn't horrible and once it's up the requests as very quick. For my needs, an the nature of the software I'm writing, lambda makes a ton of sense (mostly never used, but when it's used it's used heavily and needs to scale up high).
[0] https://sst.dev
-
Lambda to S3: Better Reliability in High-Volume Scenarios
We will start by building a project with SST that provisions an API Gateway, a Lambda, and an S3 bucket. Once implemented, we'll look into testing for concurrent write conflicts or exceeding capacity limits.
-
How I saved 90% by switching NATs
I recently deployed a node websocket server using the SST Service construct. Until this point my stack had been functions and buckets. While I had no users 😢, I also had no costs 🤡.
-
Ask HN: What web development stack do you prefer in 2024?
Most my personal and side-business projects have very spiky load or just low load in general. Because of that I love using AWS Lambda as my backend since it scales to 0 and scales to whatever you have your limits set at.
I use SST [0] for my backend with NodeJS (TypeScript) and Vue (Quasar) for my frontend. For my database I use either Postgres or DynamoDB if the fit is right (Single Table Design is really neat). For Postgres I like Neon [1] though their recent pricing changes make it less appealing.
[0] https://sst.dev
[1] https://neon.tech
-
Meta's serverless platform processing trillions of function calls a day (2023)
Yup. Entire core business product for a succeeding startup, though it's a small team of contributors (<10), and a much smaller platform team. Serverless backend started in 2018. Been a blessing in many regards, but it has its warts (often related to how new this architecture is, and of course we've made our own mistakes along the way).
I really like the model of functions decoupled through events. Big fan of that. It's very flexible and iterative. Keep that as your focus and it's great. Be careful of duplicating config, look for ways to compose/reuse (duh, but definitely a lesson learnt) and same with CI, structure your project so it can use something off-the-shelf like serverless-compose. Definitely monorepo/monolith it, I'd be losing my mind with 100-150 repos/"microservices" with a team this size. If starting now I'd maybe look at SST framework[0] because redeploying every change during development gets old fast
I couldn't go back to any other way to be honest, for cloud-heavy backends at least. By far the most productive I've ever been
Definitely has its warts though, it's not all roses.
[0] http://sst.dev
-
Building a sophisticated CodePipeline with AWS CDK in a Monorepo Setup
Along the way, you find an excellent framework, SST. Which is much faster than CDK and provides a better DX1. Here is how you then define your MultiPipelineStack.
-
Create a Next.js Server Component S3 Picture Uploader with SST
SST is a powerful framework that simplifies the development of serverless applications. It offers a straightforward and opinionated approach to defining serverless apps using TypeScript. Built on top of AWS CDK, SST handles the complexity of setting up your serverless infrastructure automatically. SST is an open-source framework and is completely free to use.
- SST – modern full-stack applications on AWS
-
Do you believe AI will replace your job?
SST is an open-source framework designed to facilitate the development and deployment of Serverless stacks on AWS. It operates under the hood by integrating with Amazon CDK. However, its primary benefit is in allowing us to concentrate on creating resources using familiar languages like TypeScript, treating them as Infrastructure as Code (IaC).
What are some alternatives?
react-slingshot - React + Redux starter kit / boilerplate with Babel, hot reloading, testing, linting and a working example app built in
LocalStack - 💻 A fully functional local AWS cloud stack. Develop and test your cloud & Serverless apps offline
win11React - Windows 11 in React 💻🌈⚡
vite - Next generation frontend tooling. It's fast!
ultra - Zero-Legacy Deno/React Suspense SSR Framework
aws-cdk - The AWS Cloud Development Kit is a framework for defining cloud infrastructure in code
esbuild - An extremely fast bundler for the web
docker-lambda - Docker images and test runners that replicate the live AWS Lambda environment
graphql-starter-kit - 💥 Yarn v2 based monorepo template (seed project) pre-configured with GraphQL API, PostgreSQL, React, Relay, and Material UI. [Moved to: https://github.com/kriasoft/graphql-starter]
serverless-offline - Emulate AWS λ and API Gateway locally when developing your Serverless project