static-web-apps-cli VS editorconfig-vim

In conjunction with the SWA CLI tool from Microsoft:[https://github.com/Azure/static-web-apps-cli](https://github.com/Azure/static-web-apps-cli)

You can find the documentation here, and the tool itself is open sourced and can be found here

I found a tool created by Microsoft which provides cli support to manage and deploy to static website. The tool called Azure Static web app CLI. The tool provides more than deployment functionality, but has lots of features to emulate authentication, and provide proxy for the API calls from the static web site.

Azure Static Web Apps CLI.

Azure Static Web Apps CLI. This is the command line interface to develop and deploy Azure Static Web Apps. Install this tool globally by running this command in the terminal: npm install -g @azure/static-web-apps-cli.

Azure Static Web Apps. It is meant for SPA frontends and Azure Functions out of the box and has a generous free tier. Very simple to use and deploys straight from github, azure devops, or the command line.

With the release of the new SWA CLI, it's never been easier to get started with Azure Static Web Apps! With the new commands you can configure your project to test it locally with the emulator, and deploy it directly from the CLI in a few minutes. It also support multiple configurations, and it's compatible with monorepos. Watch the video to learn how to get started with the new commands.

You may have missed it, but the new Azure Static Web Apps CLI is now available!

These are tools that you need to add. But the most elemental code formatting is not here, it is in the widely supported .editorconfig file.

Hello,

Maybe you should check this project:

https://editorconfig.org/

Regards,

editorconfigchecker. A linter that checks files for compliance with editorconfig rules. Another linter that helps maintain consistency in the format of all files.

Oh, yeah, we had that issue too and solved it pretty successfully with `.editorconfig` (shareable between VScode and IntelliJ, https://editorconfig.org/) combined with `prettier`.

Each IDE is configured to:

- Not reformat code on its own

- Ignore whitespace

- Run `prettier` as a pre-commit hook

Those settings are saved to `.editorconfig` where possible, or to each IDE's repo-specific folder (e.g. `.idea`).

Then in theory each developer can use whatever IDE they want, whatever whitespace settings they want (tabs vs spaces), and the end code committed to the repo is still the same.

I am aware of .editorconfig, and one day that may be the correct answer but the specification does not support every element of the styles of both oss and css.

Does this mean I can completely get rid of this plugin?: https://github.com/editorconfig/editorconfig-vim

[1] https://editorconfig.org

I dunno who downvoted your question, but I believe you can use .editorconfig to set that up for you.