Add @ndriadev/vite-plugin-universal-api to README

[nDriaDev]

Please make sure all the requirements are satisfied, otherwise the PR could be closed without further notice.

Checklist

• Title as described.
• Make sure you put things in the right category.
• The description of your item should be a sentence with less than 24 words.
• Avoid using links and parentheses in description.
• Omit unnecessary words already provided in the context (e.g. for Vite, a Vite plugin).
• Use proper case for terms (e.g. GitHub, TypeScript, ESLint, etc.)
• When mentioning tools, omit versions whenever possible (e.g. use TypeScript instead of TypeScript 4.x, but keep Vue 2 and Vue 3 as they're incompatible).
• When mentioning package names, use quotes whenever possible.
• Always add your items to the end of a list.

Plugins/Tools

• The plugin/tool is working with Vite 2.x and onward.
• The project is Open Source.
• The project follows the Vite Plugins Conventions.
• The plugin uses Vite-specific hooks and can't be implemented as a Compatible Rollup Plugin.
• The repo should be at least 30 days old.
• The documentation is in English.
• The project is active and maintained (inactive projects for longer 6 months will be removed without further notice).
• The project accepts contributions.
• Not a commercial product.

Starter Templates

• The starter template is working with Vite 2.x and onward.
• The documentation is in English.
• The starter template must provide enough instructions / documentation about how to start up and what's included.
• A screenshot or a live demo should be included.
• The repo should be at least 30 days old.
• Should be differentiable from the existing starter templates.

Apps/Websites

• The website is available without errors and load in a reasonable amount of time.
• The website must be Open Source and showing it's using Vite intensively.
• The website is original and not too simple. For that reason, blogs and simple landing pages are rejected.

[nDriaDev]

Hi! This PR has been open for a while and is currently awaiting workflow approval. I've double-checked the contribution guidelines: the description is under 24 words, it's in the correct category, and there are no merge conflicts. Could a maintainer please approve the workflow run? Thank you!

[Jogai]

Not a maintainer here, but to me it looks really good. Tiny question. How would you use this in a scenario where one would use this only in the (local) development scenario?

[nDriaDev]

Not a maintainer here, but to me it looks really good. Tiny question. How would you use this in a scenario where one would use this only in the (local) development scenario?

Thank you for the appreciation. To answer your question, if you mean how it must be configured to work in development mode, the plugin has all the configurable options to decide whether it should work only with dev mode or also in preview mode, it cannot be used in production or once the app is built because being a vite plugin, it needs vite support to work.
If your question was an example of a real possible usage scenario, the plugin is designed to support the development of a frontend app:

• if the app needs to call a backend API that has not yet been implemented, using the plugin the developer can simulate the call and verify all the scenarios.
• if the app needs to call a paid API, using the plugin the developer can mock it and implement it correctly in his app avoiding always making real calls.
  More complex use cases can also be covered. I hope I have answered your question

[Jogai]

Thank you for answering. That makes sense. And I guess its on the developer to configure the app so it uses real endpoints when its in production, but maybe it would be nice to describe configuring that, even if its just a tiny example using something simple as the fetch api.

[nDriaDev]

Thank you for answering. That makes sense. And I guess its on the developer to configure the app so it uses real endpoints when its in production, but maybe it would be nice to describe configuring that, even if its just a tiny example using something simple as the fetch api.

Thanks for the advice. I have updated the documentation and also the readme to better describe everything.