-
Notifications
You must be signed in to change notification settings - Fork 139
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Functionality to move NodeJS builtin modules to the top #71
Comments
node:
scheme / prefix to top?
Hi @karlhorky. Thank you so much for the message. We can implement this feature in the next upcoming release. If someone would like to contribute and implement this, that would be great. Please keep the following things in mind.
Feel free to drop a message if something is not clear. |
Nice, thanks for the reply! Would suggest using the following replacements for the naming:
eg. |
Any update on this? If not, I could take a look. |
Howdy! I've picked this up and a PR will be incoming momentarily. |
In case anyone here is still looking for this, until this project adds support, you could use my fork, which is published on npm and supports this feature: https://github.com/IanVS/prettier-plugin-sort-imports#importorderbuiltinmodulestotop |
Maybe it could be a |
Hi there, thanks for this package, really cool! Will consider recommending it to our bootcamp students at @upleveled.
One suggestion that came to mind would be to make it the default sort order to sort imports using the new
node:
scheme / prefix to the top. What do you think?The text was updated successfully, but these errors were encountered: