Closed vicb closed 1 month ago
Latest commit: 1dc806d892d9124ec0ae686f1449ffce3987bc62
Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.
Click here to learn what changesets are, and how to add one.
Click here if you're a maintainer who wants to add a changeset to this PR
In workers-sdk and in the vite-plugin-cloudflare projects we use Prettier to do the import ordering. See https://github.com/flarelabs-net/vite-plugin-cloudflare/pull/30/commits/1ad143fc19100534e473ac7873007a2e37d6bf55
This is nice because most people have formatting set up on-save in their IDEs, which keeps imports sorted all the time and avoids having to run eslint fix commands.
Could we consider that approach?
In workers-sdk and in the vite-plugin-cloudflare projects we use Prettier to do the import ordering. See flarelabs-net/vite-plugin-cloudflare@1ad143f
This is nice because most people have formatting set up on-save in their IDEs, which keeps imports sorted all the time and avoids having to run eslint fix commands.
Could we consider that approach?
Can we merge this PR to "unblock" me now and I'll create an issue for the follow up?
edit: it's also easy to run ESLint on save so that you does not have to execute the command edit2: also I have been delayed a bit but I still plan to work on a common eslint/prettier config to use across projects.
The previously used
sort-imports
can not fix the code.Changed the plugins to ones that can auto-fix the code (i.e. on save, or via
lint:fix
). Getting an error without auto-fix was becoming frustrating.