Thanks for implementing this really useful idea! I need to run Prettier in a variety of environments where I don't know whether a compatible Node installation is available.
I maintain run-that-app, a cross-platform application runner for such dev tools, and am currently adding support for prettier-standalone.
One thing that would simplify version selection and compatibility checks for your downstream users is aligning the prettier-standalone version with the bundled prettier version.
For example, today prettier-standalone@0.24.0 runs prettier@3.5.3.
It would be more intuitive if prettier-standalone@3.5.3 bundled and ran prettier@3.5.3.
Thanks for implementing this really useful idea! I need to run Prettier in a variety of environments where I don't know whether a compatible Node installation is available.
I maintain run-that-app, a cross-platform application runner for such dev tools, and am currently adding support for
prettier-standalone.One thing that would simplify version selection and compatibility checks for your downstream users is aligning the
prettier-standaloneversion with the bundledprettierversion.For example, today
prettier-standalone@0.24.0runsprettier@3.5.3.It would be more intuitive if
prettier-standalone@3.5.3bundled and ranprettier@3.5.3.