openapi-directory
msw
openapi-directory | msw | |
---|---|---|
11 | 148 | |
3,664 | 14,848 | |
1.0% | 1.4% | |
9.2 | 9.2 | |
2 days ago | 4 days ago | |
TypeScript | ||
Creative Commons Zero v1.0 Universal | 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.
openapi-directory
-
What is API Discovery, and How to Use it to Reduce Your Attack Surface
Use APIs.gurufor exploring well-documented OpenAPI files. For example, imagine you are interested in integrating a weather API. By searching for "weather" on APIs.guru, you find several options.
-
How to Automatically Consume RESTful APIs in Your Frontend
Furthermore, since we can split the generated code into multiple parts based on tag filtering, we can also create different SDKs from different resources or even publicly available APIs. There is an extensive list of publicly available OpenAPI specifications on SwaggerHub, RapidAPI and APIs.guru.
-
ApiVault: One-Stop Resource for API Integration
Maybe you'd like to integrate with APIs.guru?
https://apis.guru
- Show HN: An open-source OpenAPI package manager – openpm.ai
-
Automatic npm publishing, with GitHub Actions & npm granular tokens
In this specific case, I'm auto-publishing (now fully automatically, once a month) a package that wraps content from elsewhere bundling it with some utilities to make that useful in JS and available via NPM. For cases like this it's useful to have a patch update once a month that just updates the upstream content & republishes.
-
APIRank.dev - we crawled and ranked 5651+ public APIs from the internet 🔭
- Crawl API repositories like apis.guru
-
Making a useful REST API Specification
This should go without saying, but the types inside your API specification should be specific in order to be useful. The main way I see this appear is that some specification generators seem to default to "string" for everything, even if something else makes sense. In an analysis of 1154 specifications from OpenAPI directory, I found that 60% of the field types were strings. Many of these were instances that made sense, such as IDs or names, but many were misused types: for example, there was a year value encoded with type "string," and a boolean value with type "string" and enum "true" or "false". Using too-broad types such as strings can make it harder to understand the specification, and decrease the effectiveness of certain tools.
-
Data noob here - I’m looking to create my first ‘data’ project.. I want to create a basic data pipeline via an API with Python into SQL then to Power BI.. what are some well known live data sources that I should practice with?
I haven’t used it but have skimmed through it, but https://apis.guru has collected information on lots of APIs. You might find something interesting.
-
From OpenAPI to a working integration in minutes
Try the integration designer with your OpenAPI documents. If you don’t have any document handy, we prepared a few examples for you, or you can find more OpenAPI documents on APIs.guru.
-
What in your opinion is a growing trend? What should people and organisations be paying attention to going forward?
apis.guru is a nice site with APIs listed for many orgs.
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?
postman-contract-test-generator - Postman collection and environment that will take an Open API Spec, validate component adherence, generate contract tests, and execute them.
Nock - HTTP server mocking and expectations library for Node.js
atoz - Amazon Web Services (AWS) APIs in Nim
rtk-query - Data fetching and caching addon for Redux Toolkit
SpaceX-API - :rocket: Open Source REST API for SpaceX launch, rocket, core, capsule, starlink, launchpad, and landing pad data.
miragejs - A client-side server to build, test and share your JavaScript app
prism - Turn any OpenAPI2/3 and Postman Collection file into an API server with mocking, transformations and validations.
mockoon - Mockoon is the easiest and quickest way to run mock APIs locally. No remote deployment, no account required, open source.
awesomekql - Microsoft Sentinel, Defender for Endpoint - KQL Detection Packs
openapi-directory-js - Building & bundling https://github.com/APIs-guru/openapi-directory for easy use from JS
axios - Promise based HTTP client for the browser and node.js