Great job by the Next.js team on this release, I just updated my Next.js boilerplate project to 15.3: https://github.com/ixartz/Next-js-Boilerplate
It works perfectly!
HN user
Great job by the Next.js team on this release, I just updated my Next.js boilerplate project to 15.3: https://github.com/ixartz/Next-js-Boilerplate
It works perfectly!
Yes, it's very cool alternative and it removes the need for docker compose for dev environment.
On top of it, PGlite also perfect for CI and testing.
I confirm it works perfectly in CI and locally. I'm using it in CI and locally.
Not sure about Prisma but it works with Drizzle ORM.
Huge fan of PGlite.
It's the perfect solution to have Postgres without the need of Docker. With just `npm install`, you can have a Postgres instance on your computer. So, it's extremely easy to onboard a new developer in your team.
And, the good news, PGlite works perfectly with Next.js.
I'm using PGlite in local and development environment with Next.js Boilerplate: https://github.com/ixartz/Next-js-Boilerplate
With only one command `npm install`, you can have a full-stack application, which also includes the database (a working Postgres). And, no need to have/install external tools.
You can take a look at: https://github.com/ixartz/SaaS-Boilerplate, it should give you some inspiration to structure your React apps with folder structure, component breakdown.
Yes, they can try what I've built at https://pro-demo.nextjs-boilerplate.com
I didn't get the change to customize the default and built-in components from Clerk. So, it's hard for me to share any experience. But, I know you can do little customization using https://clerk.com/docs/components/customization/overview and play with CSS and Tailwind CSS. Maybe, for complex customization, it's preferable to not use the pre-built components and build it yourself.
Currently, I just feel the default UI from Clerk works good with Shadcn UI, both works great together. Definitively not perfect but do a great to job for a solo developer or for a small team.
And, I mostly using for advanced authentication features like user impersonation, multi-tenancy, roles & permission.
Just update my free and open source Next.js Landing Page template to version 14 without any issue: https://github.com/ixartz/Next-JS-Landing-Page-Starter-Templ...
It took me 5 months to build my first SaaS from scratch, which is way too much. For example, I could use this time to focus on marketing.
During my development process, I realized that 80% of the features I implemented were also present in other SaaS products. This is why I created Nextless.js, a SaaS Boilerplate that includes all the necessary features for launching a successful SaaS.
The example you have mentioned only uses Python in the backend. It's based on Django or Flask. Then, in the frontend, it uses JavaScript.
Building a SaaS from scratch required a lot of time. Happy to see a 100% Python SaaS Starter kit, usually it was reserved for JavaScript because of the frontend. In the past, you are forced to use JavaScript for the frontend.
I know it because I'm the author of Nextless.js [1], a full-stack JavaScript starter kit that is totally based on JavasScript, from frontend to backend. Using only one programming language was my competitive advantage compared to the boilerplate based on Ruby, Python or PHP.
I think in the future more and more languages can be used in the frontend like Rust, etc... There are already some frameworks you can use to build frontend in Rust. It's only the beginning.
---
I was heavily inspired by Bullet Train to build https://nextlessjs.com using JavaScript ecosystem.
It's so amazing to see how the tech community inspires and learns from one another. Laravel found inspiration from Rails. Then, seeing Bullet Train was inspired back from the Laravel ecosystem with Laravel Spark.
In the past, I was jealous of the Ruby ecosystem with an extremely large community (the grass is always greener on the other side?). And, thinking the JavaScript ecosystem was left behind, but now I am hopeful that the JavaScript ecosystem has finally caught up.
I can totally confirm Bullet Train is an inspiration for many SaaS Boilerplates. I was personally inspired by Bullet Train to build Nextless.js [1], a Next.js based SaaS Boilerplate, bringing SaaS starter kits in Next.js/React/JavaScript ecosystem.
--- [1]: https://nextlessjs.com
Thank you Vercel team, it works perfectly! Just updated my Next.js Boilerpalte to version 13.3 without any issue: https://github.com/ixartz/Next-js-Boilerplate
A picture is worth a thousand words, I'm currently writing the blog post but I believe the diagram is already representing 80% of the blog post.
Thank you for your response
I want also to implement the custom domains for my own project and you are currently using Amazon AWS to handle custom domains and auto-generates an SSL cert? If I'm not wrong Amazon AWS for custom domain is limited to a fixed number of certificate (something less than 1000). How do you plan to scale support a large amount of the customer?
Couldn't wait to see a review about Next.js! I'll happy to read it!
Thank you for taking the time to write this article.
I have close look on Remix.run, I'll definitively try in the future. It looks extremely promising. Currently, still using Next.js for all my projects.
Huge release! Thank to the hard work and the team.
I'll try the On-demand ISR right away, almost waited one year. I have just updated my Next.js to version 12.1: https://github.com/ixartz/Next-js-Boilerplate
I didn't get any issue with the update, it's already an excellent news!
Could you elaborate? I'm currently looking for a solution to build email with Tailwind CSS. So, with Maizzle you can do more things?
Currently, Stripe is addressing this issue. Couple months ago, they released Stripe Tax... I didn't have the chance to try it but it seems very promising and it's only the first version.
It's quite enjoyable to develop in cutting-edge tech: React, Tailwind CSS, TypeScript, Serverless, VSCode, etc. You are now in component paradigm with typing and styled with utility class for the frontend. Fully build in static mode so no need to have a dynamic server to serve your frontend: better performance, secure, cheaper. You can also deploy at each commit to preview your front.
Thanks to cutting-edge tech, you can deploy your backend in one command and the same thing to provision your cloud infrastructure (also in one command). With Serverless, everything scale based on your traffic, you don't need to worry about over/under provision with little maintenance.
I was a web developer in 2010 and the developer experience wasn't the same. You need to rent a server, SSH to the server, install OS dependencies, install a firewall, install a webserver, install a database, log management, monitoring, etc. and still, I didn't talk about your application and business logic. Launching a SaaS in 2010 has been extremely painful.
It seems there are a lot of dependencies but every dependency is integrated into Nextless.js for a reason. It's just the bare minimum to build a high-quality SaaS product in 2021.
Nextless.js speeds up development for your SaaS with UI components, authentication, subscription, form management with developer experience in mind: type checking, linter, code formatter, editor configuration.
Not only Nextless.js will help you to build your SaaS, but it also takes care of your production environment by leveraging serverless.
On the contrary, using all these dependencies, remove a lot of burden from you and give you more time to focus on your business. No need to be an Ops engineer or UI/UX designer anymore for a small SaaS.
Still not convince? You aren't dealing with these dependencies directly, a lot of them work under the hood and Nextless.js are taking care of them. So, no need to worry about these dependencies yourself and Nextless will receive updates. You just need to focus on the things that make your SaaS unique and grow your business.
PS: Sorry for this long response ;) I started with one paragraph and make a short response. But, I end up with this huge text and I hope it responds to your questions.
Definitively, blitzjs is extremely good full-stack framework to build applications and there are a lot of things we can learn from them.
Nextless.js is different compared to blitzjs, here is the feature which aren't available in blitzjs:
- Payment integration
- Dashboard UI
- Landing Page
- Infrastructure as code
- Deploy in Serverless environment
Nextless.js focus on SaaS application and help you build your SaaS product faster.
I know it possible but I've never tried it.
Thank you for your valuable feedbacks and sharing your thought. I totally agree with your approach for a general Saas project/product and frankly speaking, I prefer as well your business model because it can bring recurring revenue instead of one-time sales.
Here in terms of Nextless.js, as the customer will have access to the source code, the revenue sharing like 3% as you suggest is extremely hard to implement. It raises a lot of technical challenge...
Perhaps in the future, this concern can be addressed somehow and your proposed business model shall be implemented. Have you had such concerns/experiences for your projects? Pricing is not an easy subject though :)
Yes, indeed, there are something similar in Rails and Django ecosystem.
All of them give access to: - Authentication
- Payment
- Dashboard UI
- Landing page
- Form management
- ...
I just made the same for Node.js/JavaScript/TypeScript ecosystem. Nextless.js also gives access to the same features in React and TypeScript. But, I also wanted to add more into the boilerplate, things that don't offer by others:
- Infrastructure as code
- Serverless for scalability and pay-as-you-go pricing with no server to manage, no docker, no kubernetes
Indeed, you can use Redwood or any other framework to build a SaaS. But, at the end, you need to set up:
- Authentication
- User dashboard
- Landing Page
- Pricing
- Form management
- Stripe integration
- Infrastructure as code
- Type checking, linter, code formatter
- VSCode
Nextless.js provides everything out-of-the-box for you to build a SaaS business and focus on the things that makes your SaaS unique. You shouldn't lose time on boring UI, setup and configuration.
Thank you for your support and message.
I've never tried it myself but there several option to build a background jobs in serverless mode: Amazon EventBridge and CloudWatch Events. You can check the documentation at https://docs.aws.amazon.com/AmazonCloudWatch/latest/events/S...
So, no need to plug any external service.
I'm totally bias but I love Serverless, you can do everything. Background jobs shouldn't stop you using Serverless ;)
Thank you for your support and extremely happy you are also building a SaaS.
Definitively, there are several ways to build a SaaS product and I also think Cloudflare Workers, FaunaDB, Auth0, Paddle, etc. is a good stack.
One good thing to use AWS, everything is centralized. Another good thing is you can use Infrastructure as code. As a developer, you can provision everything with code (TypeScript), no need to click and remember user interface.
All frontend is in "export" mode, made in static. So, no dynamic server needed to run the frontend, 100% compatible with any static hosting like Cloudflare page.
For the backend, it uses AWS lambda with API gateway and protected by AWS Cognito for private route.