Our great sponsors
Faker.js | Next.js | |
---|---|---|
66 | 2,044 | |
1,569 | 120,572 | |
- | 1.6% | |
1.7 | 10.0 | |
over 2 years ago | 5 days ago | |
JavaScript | JavaScript | |
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.
Faker.js
-
JavaScript News and Updates of January 2022
Early this month, the malicious attack on free-to-use libraries, namely color.js and faker.js, created a real uproar in the development community. These tools are used in thousands of projects and their downloading rate from npm is estimated in millions per week. To everyone’s surprise, it turned out to be an inside job. Marak Squires, the creator of these libraries, intentionally committed malicious code to his projects and published updated codebases on GitHub and npm. It is said that this sabotage was caused by unsuccessful attempts of Mr. Squires to monetize his projects. Fortunately, malicious packages were quickly removed and the attacker’s account was suspended. The story sparked a new wave of discussion in the development community on possible steps to make the development and maintenance of open-source projects more sustainable.
-
Unofficial Faker.js fork positions itself as official successor and assumes name and Open Collective sponsors
For anyone else curious about the allusion to Aaron Swartz, it can be found here and reads (as of posting):
-
This is not normal.
Sorry little boy--- I needed to update my LinkedIn profile, hire a professional to write my resume and photograph me, and work on an open-source project no one will use (or worse- work on something everyone uses)"
-
Is there something wrong with OpenSource model?
So people, I've been reading the news regarding some great packages on GitHub, like the Colors and the Faker. I understand that this isn't related entirely with the linux community, but it is something that we should pay attention.
-
Re: the faker.js debacle: A daily reminder that htmx & hyperscript are dependency free
A developer appears to have purposefully corrupted a pair of open-source libraries on GitHub and software registry npm — “faker.js” and “colors.js” — that thousands of users depend on, rendering any project that contains these libraries useless, as reported by Bleeping Computer.
-
Open source developer corrupts widely-used libraries, affecting tons of projects
I mean he also maliciously changed all of the links on a faker.js issue to point to conspiracy theories (which I am pretty sure is against Github's TOS): https://github.com/Marak/faker.js/pull/2
- What happened with fakerjs
-
The EndGame - Fakerjs
About Four (4) Days Ago, the Author of Fakerjs a popular JavaScript library with more than 2 million weekly Download from NPM Deleted the repository and replaced it with one that only has the modified ReadMe "What really happened with Aaron Swartz?" and no content, and pushed an empty package to npm as the latest version (6.6.6).
- Marak, creator of faker.js who recently deleted the project due to lack of funding and abuse of open source projects/developers pushed some strange Anti American update which has an infinite loop
- Marak adds infinite loop test to popular colors.js
Next.js
-
Vite vs Nextjs: Which one is right for you?
Vite and Next.js are both top 5 modern development framework right now. They are both great depending on your use case so we’ll discuss 4 areas: Architecture, main features, developer experience and production readiness. After learning about these we’ll have a better idea of which one is best for your project.
-
A brief history of web development. And why your framework doesn't matter
> It’s important to be aware of what you are getting if you go with React, and what you are getting is a far cry from what a framework would offer, with all the corresponding pros and cons.
Would you like to elaborate on that?
In my experience, with something as great, size/ecosystem-wise as React, there will almost always be at least one "mainstream" package for whatever you might want to do with it, that integrates pretty well. Where a lot of things might come out of the box with a framework, with a library I often find myself just needing to install the "right" package, and from there it's pretty much the same.
For example, using https://angular.io/guide/i18n-overview or installing and using https://react.i18next.com/
Or something like https://angular.io/guide/form-validation out of the box, vs installing and using https://formik.org/
Or perhaps https://angular.io/guide/router vs https://reactrouter.com/en/main
Even adding something that's not there out of the box is pretty much the same, like https://primeng.org/ or https://primereact.org/
React will typically have more fragmentation and therefore also choice, but I don't see those two experiences as that different. Updates and version management/supply chain will inevitably be more of a mess with the library, admittedly.
Now, projects like Next https://nextjs.org/ exist and add what some might regard as the missing pieces and work well if you want something opinionated and with lots of features out of the box, but a lot of those features (like SSR) are actually pretty advanced and not always even necessary.
-
System & Database Design (Day 1) - Creating a SaaS Startup in 30 Days
Next.js: For the website and the admin dashboard
-
Runtime environmental variables in Next.js 14
Until the time of writing, there is no official example of how to enable runtime environmental variables in a Dockerized Next.js app, as utilizing unstable_noStore would only dynamically evaluate variables on the server (node.js runtime). There is also an interesting discussion regarding this topic on GitHub.
-
@matstack/remix-adonisjs VS Next.js - a user suggested alternative
2 projects | 24 Apr 2024
next.js is a very popular React framework. remix-adonisjs includes more functionality through the AdonisJS backend ecosystem, and should be easier to self-host and self-manage.
-
Meet Cheryl Murphy: Full-Stack Developer, lifelong learner, and volunteer Project Team Lead at Web Dev Path
Cheryl Murphy is not only a dedicated full-stack web developer skilled in technologies like React, Next.js, and NestJs but also a community-driven professional who recently took on the role of volunteer project team lead at Web Dev Path. With a dual Bachelor's degree in Computing and Chemical Engineering from Monash University, Cheryl’s journey in tech is marked by a passion for building accessible solutions and a commitment to fostering community within tech.
-
Ensuring Type Safety in Next.js Routing
For more information, check out this issue.
-
Styling Your Site with Next.js and MUI: Creating a Dynamic Theme Switcher
Remember to start the Next.js server with pnpm dev.
- Mastering Next.js 13/14 - Advanced Techniques
- 3 Exciting Improvements Between NextJS 14 And NextJS 13
What are some alternatives?
jest-playwright - Running tests using Jest & Playwright
vite - Next generation frontend tooling. It's fast!
simplecrawler - Flexible event driven crawler for node.
Express - Fast, unopinionated, minimalist web framework for node.
casual - Fake data generator for javascript
SvelteKit - web development, streamlined
fake-store-api - FakeStoreAPI is a free online REST API that provides you fake e-commerce JSON data
MERN - ⛔️ DEPRECATED - Boilerplate for getting started with MERN stack
Electron - :electron: Build cross-platform desktop apps with JavaScript, HTML, and CSS
Angular - Deliver web apps with confidence 🚀
msw - Seamless REST/GraphQL API mocking library for browser and Node.js.
fastify - Fast and low overhead web framework, for Node.js