-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Getting Vite working with Sails.js/Parasails #7306
Comments
@sahyrlelyaams Thanks for posting! We'll take a look as soon as possible. In the mean time, there are a few ways you can help speed things along:
Please remember: never post in a public forum if you believe you've found a genuine security vulnerability. Instead, disclose it responsibly. For help with questions about Sails, click here. |
Hey @sahyrlelyaams that's a great idea, I'm currently working on the next evolution of the Sails asset pipeline called Shipwright. Like Vite, it will be based on ESBuild. |
@DominusKelvin I would like to checkout your asset pipeline solution. Have you open sourced it yet? |
Hey @sahyrlelyaams I'm the lead maintainer of Sails and Shipwright is being made as an official replacement for grunt Once a public beta is ready an announcement will be made |
Hey @sahyrlelyaams a version of Shipwright has been published and today you can use it by running |
Node version:
Sails version (sails):
ORM hook version (sails-hook-orm):
Sockets hook version (sails-hook-sockets):
Organics hook version (sails-hook-organics):
Grunt hook version (sails-hook-grunt):
Uploads hook version (sails-hook-uploads):
DB adapter & version (e.g. [email protected]):
Skipper adapter & version (e.g. [email protected]):
Basically, the title.
Is there any way of getting Vite to work with Sails.js/Parasails? Wanted to leverage the modern features of Vite with Parasails remaining to serve Vue.js pages...
The intention would be to use Vite for the frontend bundling/build pipeline instead of the Grunt task runner enabled by default.
The text was updated successfully, but these errors were encountered: