RicardoDev

joined 1 year ago
 

Hello everyone,

I’ve created this starter project for creating production ready web apps in Vite and React that I hope some might find useful. This template came about as a necessity to provide some standardization across new projects at work. A few of the initial goals when creating this project were to:

  • Reduce setup time
  • Standardize codebase with ESLint and Prettier
  • Improve commit messages with tools like husky, commitizen and commitlint
  • Improve codebase maintainability and scalability by providing a reasonable folder structure
  • Simplify React Component development through use of tools like Storybook
  • Improving codebase stability with unit and E2E tests via Vitest + React Testing Library and Playwright respectively
  • Ease the deployment process by providing a simple starter Dockerfile

In addition to all the aforementioned goals, I also wanted to use modern tools such as React Query + Zustand for state management, React Hook Form + Zod for creating and validating forms, Tailwind CSS for building out UI’s, etc.

I tried to cover everything I, and others, might need but recognize that everyones requirements are different. Luckily, this isn’t a framework so removing unneeded packages or adding new ones is as simple it would normally be. The project itself doesn’t come with a demo as its purpose is to simply provide a foundation for any new projects you might have in mind.

Feedback and questions are always welcome and I appreciate anyone willing to checkout this project.

Thank you

[–] [email protected] 2 points 1 year ago

Other way around most of the time. Instances choose who to defederate with. If you view all posts instead of local You’ll see posts across the fediverse so long as the instance owner hasn’t defederated. Defederation is also a pretty nuclear option so it’s generally not taken lightly.

[–] [email protected] 2 points 1 year ago

An instance is basically a Lemmy “app”. These “apps” or instances of Lemmy are being run on some server somewhere. Could be your own server you set up or a pre-existing one like lemmy.world setup by someone else. Each instance or “app” is also connected to every other Lemmy instance unless explicitly blacklisted. This why you sometimes see urls in peoples user names and communities. They’re posting from someone else’s Lemmy server (not the one you’re logged in to).

The idea is if one instance goes down, Lemmy as a whole will continue to run so long as one is still running. It also allows people who to host their own for whatever reason they may have, whether that be differences of opinion with existing instances or simply because they want their own set of communities.

[–] [email protected] 6 points 1 year ago* (last edited 1 year ago)

It’s already taken by another lemmy app

 

I've been working on (yet another) Lemmy app for the fun of it but I had a question come to mind with the new v0.18.0 announcement.

Since it is up to the instance admins to update the server, how should Client developers handle instances across Lemmy having different API version numbers with potential incompatibilities?

There are a few existing libraries but it seems the change from v0.17.4 to v0.18.0 is proving cumbersome for at least one library and most likely others as well.

Any thoughts?