Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

MSW 2.0 – Mock Service Worker

mswjs.io

Post reply on HN
Print view View original

21–30 of 61 posts

Re: MSW 2.0 – Mock Service Worker

#21

Post by dcre »

At my job we've found working with MSW + OpenAPI to be near miraculous. I work on a web frontend and do most of my development against a mock API powered by MSW. This live preview runs against the mock API running fully in-browser.

https://oxide-console-preview.vercel.app

More details:

https://github.com/oxidecomputer/oxide.ts

https://github.com/oxidecomputer/console

https://oxide.computer/podcasts/oxide-and-friends/1426644

Really excited about this next step for MSW — we'll be upgrading soon. Building on web standards buys you so much.

(Reposted at top level because the parent got flagged.)

Re: MSW 2.0 – Mock Service Worker

#22

Post by ngruhn »

sph wrote: post #11
teaearlgraycold wrote: post #7

Earlier quoted context omitted.

I don't think they have VC money. I think the people building it just know what they're doing. Do you see anything that indicates this is a VC-funded project? It looks to me like they're only getting a little bit of money from Github Sponsors ( https://github.com/sponsors/mswjs ).

That's a lot of time and effort, for people earning next to nothing, for an open-source library. I'm not saying it's bad they have a beautiful website to rival any small SaaS, but how is even possible they have the time and energy to spend on that, rather than on the code itself? What would Linux or GNOME or leftpad look like with a proportional amount of marketing effort? Last time I checked, testing libraries did n…

I think this is actually pretty common in the JavaScript ecosystem. Presumably, because contributors are very skilled in building websites and maybe also because users have higher expectations when it comes to presentation. I mean checkout https://vitest.dev/ https://jestjs.io/ https://webdriver.io/de/ https://playwright.dev/ (all testing related stuff).

Re: MSW 2.0 – Mock Service Worker

#23

Post by ElectricalUnion »

revskill wrote: post #14
michaelmior wrote: post #12

Earlier quoted context omitted.

I'm not sure what you're getting at here. Not all open source projects are trying to turn users into products. A lot of open source projects derive value from getting external contributions that they wouldn't otherwise if something was kept closed source and in-house. Paying for software isn't always necessary. That said, the project also has several sponsors: https://github.com/sponsors/mswjs

It's always like that. I can't find any exception, sorry. It's natural right ? You can't just have your cake and eat it, too.

Stuff like Blink, it's designed to be a free-as-possible, scorched-earth-tactics moat so anyone trying to be "funny" and locking down/monetizing the platform in other ways other that the major contributor "blessed ways" are screwed up.

In a way, the "freeest" tech around is the one that promotes "commoditize your complement", as that is the most capitalist incentive one has to have your cake and eat it, too.

> Along the way, I noticed something interesting about open source software, which is this: most of the companies spending big money to develop open source software are doing it because it’s a good business strategy for them, not because they suddenly stopped believing in capitalism and fell in love with freedom-as-in-speech.

> (...) All else being equal, demand for a product increases when the prices of its complements decrease.

> Let me repeat that because you might have dozed off, and it’s important. Demand for a product increases when the prices of its complements decrease.

> https://www.joelonsoftware.com/2002/06/12/strategy-letter-v/

Re: MSW 2.0 – Mock Service Worker

#28

Post by flakes »

candylifter wrote: post #2

Nice to see more and more tools adopting standard Fetch API Request/Response interfaces.

Agreed. The more non-intrusive your APIs are, the better the overall experience is going to be for developers. Diverging from official/standard APIs means higher chance framework lock-in, which has kept me away from a lot of tooling.

Always try to ask myself when adding tooling: What's the chance I'll want to remove this later, and how painful is that going to be?

Re: MSW 2.0 – Mock Service Worker

#30

Post by berziunas »

dcre wrote: post #21

At my job we've found working with MSW + OpenAPI to be near miraculous. I work on a web frontend and do most of my development against a mock API powered by MSW. This live preview runs against the mock API running fully in-browser. https://oxide-console-preview.vercel.app More details: https://github.com/oxidecomputer/oxide.ts https://github.com/oxidecomputer/console https://oxide.computer/podcasts/oxide-and-friends/…

Is it ok if I see I am logged in as as Hannah and can launch new instances after clicking the first link?
Post reply on HN