overreacted.io
Nest
overreacted.io | Nest | |
---|---|---|
46 | 312 | |
6,995 | 64,419 | |
- | 1.3% | |
7.3 | 9.9 | |
3 months ago | 5 days ago | |
JavaScript | TypeScript | |
GNU General Public License v3.0 or later | 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.
overreacted.io
-
Show HN: DanGPTāDan Abramov as a GenAI with RAG
He's a React maintainer. He has a blog and a Twitter account which gained him quite some fame in the JavaScript world.
https://overreacted.io/
-
āIām leaving my job at metaā
This is a whole thread (not a single tweet). Unfortunately Elon Musk's Twitter no longer shows threads to logged out users. :(
For convenience, I'll copy and paste the entire thread here:
1. i feel bittersweet sharing iām leaving my job at meta in a few weeks. working in the react org at meta has been an honor. i am thankful to my past and present colleagues for taking me in, letting me make mistakes, helping me see my strengths, being kind, and sharing their time.
2. for the past three years, i kept saying iād leave āin a year or soā but the moment never felt right. i wanted to (1) finish the new docs and (2) see a broadly usable Suspense data fetching integration shipping. after years of work from the team, both have shipped this spring.
3. i felt hesitant leaving earlier because not too long ago, leaving meta used to mean leaving the react team. that would feel too sad for me. but it is not true anymore. react has become a multi-company project, and there are several independent engineers on the team too.
4. i am staying on the react team as an independent engineer, similar to @sophiebits and @sebsilbermann . this means that i will not be actively sponsored to work full-time on react by any company, but i will stay involved in the teamās work and attend our meetings.
5. the exact nature of my future involvement is not yet clear to me. when i started on the react team seven years ago, i used to mostly write code. however, my teammates often outshine me at that, and i found myself gravitating to doing other things over time.
6. one of the things i naturally gravitated towards was explaining things. i practiced writing on http://overreacted.io, and later @rachelnabors inspired me to write http://react.dev together. i poured my heart into that project, but i bit off a bit more than i could chew.
7. what happened is that my standard for writing has gone higher but my writing ability did not. i find it difficult to write now because i canāt match the standard in my own head anymore. this will probably go away with time, but i need a little break from writing words.
8. sometimes people think i write a lot of code for react, but i havenāt been doing that for a while. aside from co-writing the new docs, the rest of my contributions in the past few years have mostly been community glue work: being a bridge between the community and the team.
9. although i enjoy this type of work, it is not sustainable to do on my own, and it has taken a toll emotionally. at some point being a single point of failure stops being fun, and i was feeling that iām failing both the team and the community. we needed to learn to scale it up.
10. over the last year, weāve been building a new wing of the react team focused on community glue work. i trust @Eli_White @kmiddleton14 @lunaleaps @mattcarrollcode @rickhanlonii to carry this torch in a sustainable way. i will stay very closely involved. https://twitter.com/dan_abramov/status/1644373027692462086
11. on the engineering side, i fully trust @en_JS technical leadership at Meta and @sebmarkbage technical leadership at Vercel. currently, only two companies are sponsoring employees to work full-time on React, but weād like to onboard contributors from other companies in the future.
12. finally, a little personal note. this is not a part of some kind of a grand plan. i donāt do āplansā and āgoalsā. i just had a hunch that now that the things i care about are not going to fall on the floor, itās the right moment to try something new and feel like a beginner again
13. idk what iāll do next yet. might do some youtube, some consulting. i do feel a bit itchy to write some product code in react with a fast iteration cycle outside of a large company. maybe iāll do a combination of all of that. i kinda want to just do nothing too. weāll see :)
14. i feel a little relieved, a little scared, but mostly thankful. iām grateful to @jingc for noticing me, @tomocchino for believing in me, and @sebmarkbage & @sophiebits for teaching me everything. work is people, and youāre the best i could hope for. see yāall at the weekly syncs!
15. [badge photo](https://pbs.twimg.com/media/F1fGaGwacAAiKfM?format=jpg&name=...)
-
Blogroll: the list of blogs that I like to read
Dan Abramov
-
How to take my React knowledge to the next level?
Also, Dan Abramov's blog is a must-read, if you haven't yet: https://overreacted.io/
-
RSC and the Echo of 'Presentational and Container Components'
In 2015 Dan Abramov published an article titled Presentational and Container Components.
-
Seeking recommendation for Engineering blogs that keep track of latest React patterns
Also, Dan Abramov's blog is must read, he's literally in React team, so both React patterns, and big tech best practices: https://overreacted.io/. A bit abandoned now, but still very useful.
-
Which are the best blogs for react?
https://overreacted.io/ - by far the best in my opinion. Doesnāt get much more in depth than Dan
-
Top 10 #Software #Developers who are so well-known throughout the #IT_world š»
7ļøā£ Dan Abramov - Prime Mover of Redux, a popular JavaScript library for managing application state, and a member of the React.js core team. Technology skills include programming languages such as JavaScript and #TypeScript.
-
How are some people are able to explain things 'scientifically' in terms of React?
- Reading Dan Abramov's blog: https://overreacted.io/
- What is a good resource to learn react online?
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?
ui.mantine.dev - Mantine UI website and components
SailsJS - Realtime MVC Framework for Node.js
react-18 - Workgroup for React 18 release.
Koa - Expressive middleware for node.js using ES2017 async functions
gatsby-plugin-dark-mode - A Gatsby plugin which handles some of the details of implementing a dark mode theme
loopback-next - LoopBack makes it easy to build modern API applications that require complex integrations.
didact - A DIY guide to build your own React
feathers - The API and real-time application framework
reactjs.org - The React documentation website [Moved to: https://github.com/reactjs/react.dev]
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!
WordPress - WordPress, Git-ified. This repository is just a mirror of the WordPress subversion repository. Please do not send pull requests. Submit pull requests to https://github.com/WordPress/wordpress-develop and patches to https://core.trac.wordpress.org/ instead.
Moleculer - :rocket: Progressive microservices framework for Node.js