lost-pixel VS wundergraph

As an example, we will run a simple GitHub action on our front-end project. GitHub action will be the bare minimum and will execute some open-source visual regression tests on a single webpage.

Hey, r/vuejs! Over the weekend, I found out about Histoire existence and that the Vue community loves the tool. I am building a visual regression testing framework(some see it as an addition to E2E tests, and some use visual tests as smoke tests because of the ease of use), and I decided to add the first-class support of Histoire to it.

in this case you could start experimenting with cloud solutions as this setup that you explained looks far more in the direction of a well established business(where you could afford paying for external services). we built lost-pixel.com exactly for this purpose, we don't support multiple browser runs at this stage but we already do support breakpoints. it's usually about optimising the tools for the use case(or rather converging the use case to existing tools if it makes the life of engineers easier) and I think there is no unsolvable problem when it comes to testing :D

- we have our engine open-sourced. You could use Lost Pixel for free outside of the Lost Pixel Platform(like loki.js)- we are not storybook tool per se(like chromatic). It allows you to compose your visual tests beyond storybook in single run- due to the nature of how we run the whole flow, we are cheaper than chromatic- chromatic is a great tool(before we wrote Lost Pixel we were using Chromatic in one my contracting gigs) but sometimes it lacks features, we want to make Lost Pixel a go to solution for visual testing, wether it be storybook, or custom testing or holistic testing.

We have worked hard on the Lost Pixel Platform - the SaaS version of our tool. We are a small team of two working on it currently, but we already have awesome clients like prisma.io and adverity.com. I would be excited if you try it out and give us the feedback if you will have any!

Maybe you could set up https://lost-pixel.com in custom mode; you would make a screenshot of Figma UI & then run it over Lost Pixel visual regression testing. Hit me up, I think I might help you to get it running! u/a-friendgineer

Hey, r/nextjs! I am a big fan of monorepos, using Turborepo in almost all of my projects, I am also a big fan of visual tests :D Prepared this short tutorial on how to get Turborepo running with Lost Pixel(Disclaimer: I've created this tool, it's OSS, btw)

Hey! We got some love some time ago here on reddit when we launched https://github.com/lost-pixel/lost-pixel so we decided to validate our idea further and build a full fledged platform to manage your visual tests. https://lost-pixel.com - welcome Lost Pixel Platform! We already have large teams using it for quite a bit of time so we decided to go into Open Beta and open our work of almost 6 months to everybody! I would be super grateful for your feedback and of course I am here to answer all of your questions and just chat. We are free for Open Source projects so if you want to use our managed version for your public OSS project just drop me a message!

Check it out - https://lost-pixel.com/Being OSS at heart our platform is free for Open Source projects!

I never really got graphql until I stumbled upon Wundergraph. (https://github.com/wundergraph/wundergraph). I have no affiliation with them except that I have been building an app with it. I'm honestly puzzled how it's not more popular. Maybe people are solving these problems in other ways? But I tried out a bunch of stuff: Vapor, Supabase, Hasura, etc. None of it simplifies building complex systems the way WG does.

I think their takes on graphql make sense: https://wundergraph.com/blog/graphql_is_not_meant_to_be_expo...

To demonstrate field usage metrics in Federation, I’ll be using WunderGraph Cosmo — a fully open source, fully self-hostable platform for Federation V1/V2 that is a drop in replacement for Apollo GraphOS.

The inverse is also true. As a technical founder, and maybe even an introvert like me, you should definitely look for a non-technical co-founder who can help you with networking, etc... I found my dream co-founder through YC Co-founder match and what can I say, it's going great. We're focusing on enterprise GraphQL/API solutions (https://wundergraph.com) and I benefit from the networking and communication abilities of Stefan, while I answer all technical questions. Tldr, I highly recommend to team up with people who complement your skills.

GraphQL Gateway is primarily responsible for serving GraphQL queries to consumers. It takes a query from a client, breaks it into smaller sub-queries, and executes that plan by proxying calls to the appropriate downstream subgraphs. When we started our journey, there was only Apollo Federation in the arena, and we used it. Still, now you can look at other options (e.g. Mercurius, Conductor, Hot Chocolate, Wundergraph, Hasura Remote Schemas), compare benchmarks and decide what's important and preferable for your needs. The Gateway provides a unified API for consumers while giving backend engineers flexibility and service isolation.

I'm a big fan of tRPC. It's amazing how it pushed TypeScript only stacks to the limit in terms of DX. Additionally, it made the GraphQL community aware of the limitations and tradeoffs of the Query language. At the same time, I think tRPC went through a really fast hype cycle and it doesn't look like we're seeing a massive move away from REST and GraphQL to RPC. That said, we see a lot of interest in RPC these days as we've adopted some ideas from tRPC and the old NextJS. In our BFF framework (https://wundergraph.com/) we've combined file based routing with RPC. In addition to tRPC, we're automatically generating a JSON Schema for each operation and an OpenAPI spec for the whole set of operations. People quite like this approach because you can easily share a set of RPC endpoints as an OpenAPI spec or postman collection. In addition, there are no discussions around HTTP verbs and such, there's only really queries, mutations and subscriptions. I'm curious what other people's experiences are with GraphQL, REST and RPC style APIs? What are you using these days and how many people/teams are involved/using your apis?

You can check out the source code on GitHub and leave a star if you like it. Follow me on Twitter, or join the discussion on our Discord server.

If you like the work we're doing and want to support us, give us a star on GitHub.