pivot
msw
pivot | msw | |
---|---|---|
4 | 150 | |
15 | 14,946 | |
- | 2.1% | |
8.5 | 9.2 | |
9 months 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.
pivot
- What are some of the best libraries you cannot work without?
-
Writing Integration Tests that Run Inside a Unit-testing Framework like Jest
We can construct our apps in a way that is headless, where the app itself works without needing to render anything to the DOM. This is what I'm doing with the Pivot framework. An app is created without anchoring to a DOM element, like this:
-
What is not taught in React courses, but is commonly used in a real job and overlooked?
The main benefit for me is testing. For example here I'm integration testing the app inside Vitest, so integration tests take just a few milliseconds and can be debugged much more easily in the IDE.
-
Redux vs Redux toolkit
I've done something similar. I love redux, but RTK is absolutely overkill and tightly couples your business logic to the framework. I ended up creating my own createSlice function and side-effects services: https://github.com/andyjessop/pivot/tree/main/packages/lib/slice
msw
-
Modern React testing, part 5: Playwright
We’re going to use Mock Service Worker (MSW) for mocking network requests in our integration tests and in the app during development.
-
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.
What are some alternatives?
developer-roadmap - Interactive roadmaps, guides and other educational content to help developers grow in their careers.
Nock - HTTP server mocking and expectations library for Node.js
nivo - nivo provides a rich set of dataviz components, built on top of the awesome d3 and React libraries
rtk-query - Data fetching and caching addon for Redux Toolkit
vitest - Next generation testing framework powered by Vite.
miragejs - A client-side server to build, test and share your JavaScript app
Immer - Create the next immutable state by mutating the current one
mockoon - Mockoon is the easiest and quickest way to run mock APIs locally. No remote deployment, no account required, open source.
bulletproof-react - 🛡️ ⚛️ A simple, scalable, and powerful architecture for building production ready React applications.
prism - Turn any OpenAPI2/3 and Postman Collection file into an API server with mocking, transformations and validations.
devtools - Replay.io DevTools
axios - Promise based HTTP client for the browser and node.js