Faker.js
msw
Our great sponsors
Faker.js | msw | |
---|---|---|
66 | 148 | |
1,569 | 14,808 | |
- | 2.3% | |
1.7 | 9.3 | |
over 2 years ago | 6 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.
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
msw
-
Easier TypeScript API Testing with Vitest + MSW
However, I discovered a great combination that transformed my API call testing in TypeScript: Vitest and Mock Service Worker (MSW). Their well-crafted design makes them incredibly easy to use, enhancing the overall testing experience.
-
Creating mocks for testing react code
While mocks are effective, they require modifying the component's internal logic or mocking global functions like fetch. This can become cumbersome for complex components with numerous API interactions. Here's where MSW shines.
-
Storybook 8
> For those wondering what the use case is, you must not have tried it. It does take work to set up (with each version that's less), but it can be very nice to test in isolation esp in cases where a component is under a login, the 4th page of a 10 page form, etc. Also obviously if you're working on a component library that ships without an app, Storybook can be your development and/or demo app.
I have worked with storybook extensively over the past couple of years and my team is moving away from it in favour of MSW (https://mswjs.io).
For "4th page of a 10 page form" during the development there's hot reloading which is really stable nowadays and haven't failed me, although I understand that some setups are old and it might be easier to configure Storybook than good hot reloading.
I'm not entirely sure about the testing part of it and I'd be grateful if you could elaborate. I haven't felt the need for some special setup with SB because for unit tests, I can test a deeply nested component separately. For E2E tests, I usually test the whole form.
I agree on the component library part, this is probably the only use case where Storybook is 100% justified, but I'm unconvinced about the
Additionally, thank you to all our community launch partners across the frontend ecosystem for helping us bring Storybook 8 to the world! Thanks to Chromatic, Figma, ViteConf, Omlet, DivRiots, story.to.design, StackBlitz, UXpin, Nx, Mock Service Worker, Anima, Zeplin, zeroheight, kickstartDS, and Kendo UI.
-
I made "TypeScript Swagger Editor", new type of Swagger UI writing TypeScript code in the browser
similar with msw.js, but fully automated
-
Partial: how not to mock the whole world
they could be network mocks (use msw)
-
How to Automatically Consume RESTful APIs in Your Frontend
With orval, we can also integrate the API client in our unit tests. Orval provides first class support for mocking through the (Mock Service Worker)[https://mswjs.io/] library, and it can automatically generate the MSW handlers for testing server.
- Polly.js – Record, replay, and stub HTTP interactions
-
How to Successfully Integrate with Legacy APIs Using NodeJS
Consider a hypothetical scenario where data from a list of companies within an ERP needs to be retrieved. As a personal recommendation, leverage tools like MSW for top-level mocks, which can significantly enhance the testing process.
- How do you manage Dependency Injection in Next.js APPS?
What are some alternatives?
jest-playwright - Running tests using Jest & Playwright
Nock - HTTP server mocking and expectations library for Node.js
simplecrawler - Flexible event driven crawler for node.
rtk-query - Data fetching and caching addon for Redux Toolkit
casual - Fake data generator for javascript
miragejs - A client-side server to build, test and share your JavaScript app
fake-store-api - FakeStoreAPI is a free online REST API that provides you fake e-commerce JSON data
mockoon - Mockoon is the easiest and quickest way to run mock APIs locally. No remote deployment, no account required, open source.
Electron - :electron: Build cross-platform desktop apps with JavaScript, HTML, and CSS
prism - Turn any OpenAPI2/3 and Postman Collection file into an API server with mocking, transformations and validations.
os-locale - Get the system locale
axios - Promise based HTTP client for the browser and node.js