payload
Nest
payload | Nest | |
---|---|---|
160 | 315 | |
20,556 | 64,989 | |
4.6% | 0.9% | |
9.9 | 9.9 | |
1 day ago | 7 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.
payload
- Best way to build a modern back end and admin UI. No black magic
-
Headless CMS: Directus vs Payload vs Strapi in 2024
Despite being a relatively newer player, Payload's GitHub repository has accumulated 18.8k stars and 1.1K forks as of April 2024, reflecting its growing community. The project has also secured $5.6 million in funding, positioning it for continued growth and innovation.
-
Ask HN: Freelance website builders/maintainers, what's in your 2024 toolkit?
My most recent project launched in January. NextJS 14 client integrated with PayloadCMS (http://payloadcms.com) for the back-end. I love both technologies in theory, but they're both going through a renaissance period and "bleeding edge" doesn't even begin to describe it.
If I'm just building a client app, create-react-app is still my go to.
Before now, I'd been building on WordPress for 10+ years for anything client-administered. Planning on using Payload from here on out.
-
Open-Source Headless CMS in 2024
Payload CMS: The Customization Insurgent
-
Prismic.io is increasing our price by *1900%* over Christmas
Payload is free, you can self host it without paying a one time fee or a SaaS fee for its use, it even says so at the bottom of the homepage
-
Next.js 14: No New APIs & Breaking Changes
James, the co-founder of Payload, a headless CMS with MongoDB support, shared his insights on the drawbacks and limitations of using a headless CMS in the context of web development. He challenged the promises often made about headless CMS, such as separation of concerns and ease of content migration, revealing that these claims often don't align with the reality faced by developers and clients. James is considering integrating Payload directly with Next.js to overcome these limitations and offer a better developer experience, including out-of-the-box features and simpler deployments. Should Payload move to Next.js?
- Ask HN: Why aren't Django Admin style dashboards popular in other frameworks?
- Payload (app framework + CMS in TypeScript) releases 2.0
- Payload 2.0: Postgres, Live Preview, Lexical RTE, and More
-
Payload 2.0 released, TypeScript headless CMS and app framework
Hey HN, Dan here from Payload (YC S22), an open-source headless CMS that closes the gap between CMS and traditional app frameworks. Weâre excited to announce Payload 2.0!
https://github.com/payloadcms/payload
If youâve not heard of Payload youâre probably wondering why the world needs another CMS. Payload connects to your database and runs without the vendor lock-in and black box of SaaS based CMS solutions, and itâs far more extensible than off-the-shelf SaaS options. Enterprises in specific have been finding value in this control, and theyâre using Payload to power content infrastructure that simply isnât possible through integrating with SaaS webhooks alone.
Todayâs announcement is all about features that strike at two neglected areas in the world of CMS. The first is application framework level control over your database that youâd expect with tools like Ruby on Rails or Laravel and the second area is making content editors effective by seeing their edits in realtime.
Here are the highlights on what weâve been working on:
*Postgres Support*âin the same week we launched about two years ago,people asked for Postgres support. It brings me pure cathartic joy to finally give this to our community. To be fair, MongoDB has been a perfect solution for our architecture and itâs still recommended. But with a new adapter pattern for databases, you can stand your Payload project up on Postgres and run the same functionality as you can with MongoDB now. The crazy part is that we didnât compromise on how nesting complex fields works. We could have taken the âeasyâ road and wrote things to JSON, but we leaned fully into the relational way and built the right tables and native column types for fields all the way throughout.
*Database Migrations*âmaintaining a production app while deploying schema changes is something you come to expect from ORMs and backend frameworks, but rarely CMS. Payload 2.0 delivers full, first-party migration support all in TypeScript. We took a lot of care on the developer experience here so that when working with Postgres, thanks to our friends at Drizzle, we generate the migration files in TS that add the tables and fields for you. If you have to manipulate data before or after, you have a clear way forward now.
*Database Transactions*âwhen a request involves multiple inserts, updates or deletes to the database, you need control to rollback all changes when one part fails. The built-in Payload CRUD operations do this now for you and your custom hooks and other code can too.
*Live Preview*âthe ability to quickly draft content and see it in context of a website is a literal game changer. We have taken the best dev experience of any headless CMS and given the editors a reason to demand Payload over the others.
*Lexical Richtext Editor*âour original Slate based editor has seen some great features added, like storing related documents directly in the JSON, uploads and any customizations. Unfortunately Slate leaves a lot to be desired on how to extend it, especially compared to Lexical. In a few short weeks weâve built up a new editor experience inspired by Medium and Notion. Now type â/â and have embedded relationships, uploads, and custom blocks popping right up to be dropped in. Then drag and drop them to reorder your content. If you still want Slate, we continue to support that too.
Weâre not compromising on editor experience. This is how weâre bringing the âheadâ to the headless CMS.
Building critical applications on top of a CMS may sound like blasphemy but it doesnât have to be that way.
Thanks for reading! I look forward to hearing what you think.
Nest
-
NestJS tip: how to change HTTP server timeouts
When using the NestJS framework, sometimes you may need to change some default timeout. You can define them just like you'd do in a plain Node.js HTTP server like so:
-
Containerize your multi-services app with docker compose
Back: a graphQL server built with Nestjs
-
Full Stack Web Development Concept map
NestJS - opinionated more scalable, but harder to learn docs
-
Don't go all-in Clean Architecture: An alternative for NestJS applications
Pragmatically, we can apply this to a Nest application by creating an Interface for our services, separating the Presenter layer (Controller) from the Use Case (Services):
- Utilizando Testcontainers para Testes de Integração com NestJS e Prisma ORM
-
A Gentle Introduction to Containerization and Docker
Itâs a text document that contains all the commands a user could call to assemble an image. Letâs check an example of a Dockerfile for a nodejs app in this case it will be a NestJS app and then explain each part.
-
Scalable REST APIs with NestJS: A Testing-Driven Approach
describe('Create bookmarks', () => { const dto: CreateBookmarkDto = { title: 'NestJS', link: 'https://nestjs.com/', }; it('should create bookmark', () => { return pactum .spec() .post('/bookmarks') .withHeaders({ Authorization: 'Bearer $S{userAt}', }) .withBody(dto) .expectStatus(201) .stores('bookmarkId', 'id')//store the bookmark id in the variable bookmarkId .expectBodyContains(dto.title) .expectBodyContains(dto.link) }); });
-
Rust GraphQL APIs for NodeJS Developers: Introduction
In my usual NodeJS tech stack, which includes GraphQL, NestJS, SQL (predominantly PostgreSQL with MikroORM), I encountered these limitations. To overcome them, I've developed a new stack utilizing Rust, which still offers some ease of development:
-
A Step-by-Step Guide to Implement JWT Authentication in NestJS using Passport
The purpose of this article is to provide a step-by-step guide for implementing authentication system in a NestJS project using the Passport middleware module.
-
From Frontend to Backend
That's exactly where I am. My manager gave me these links, that cover a lot of those words the backend uses, so I can identify what they mean and how to use them. 1. For inspiration and concepts: https://github.com/Sairyss/domain-driven-hexagon 2. Suggested to read the documentation for nest.js. They apply such concepts I don't understand: https://nestjs.com/
What are some alternatives?
Strapi - đ Strapi is the leading open-source headless CMS. Itâs 100% JavaScript/TypeScript, fully customizable and developer-first.
SailsJS - Realtime MVC Framework for Node.js
Directus - The Modern Data Stack đ° â Directus is an instant REST+GraphQL API and intuitive no-code data collaboration app for any SQL database.
Koa - Expressive middleware for node.js using ES2017 async functions
bulletproof-react - đĄď¸ âď¸ A simple, scalable, and powerful architecture for building production ready React applications.
loopback-next - LoopBack makes it easy to build modern API applications that require complex integrations.
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.
feathers - The API and real-time application framework
Ghost - Independent technology for modern publishing, memberships, subscriptions and newsletters.
Ts.ED - :triangular_ruler: Ts.ED is a Node.js and TypeScript framework on top of Express to write your application with TypeScript (or ES6). It provides a lot of decorators and guideline to make your code more readable and less error-prone. âď¸ Star to support our work!
KeystoneJS - The most powerful headless CMS for Node.js â built with GraphQL and React
Moleculer - :rocket: Progressive microservices framework for Node.js