-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Explore using ESBuild instead of Gulp in Core #14169
Comments
@dangvanthanh if you have something to show, I suggest you our Steering meeting on Tuesdays 12PM PST https://docs.orchardcore.net/en/latest/docs/resources/meeting/ and perform a demo. |
I am currently working on using Esbuild with Orchard Core. I will be showcasing a demo soon. |
Thanks, looking forward to it |
@dangvanthanh is this something you are still working on? When should we expect a demo? |
@MikeAlhayek currently, I can integrate using ESbuild (with PostCSS, TailwindCSS, Flowbite, TypeScript, and Vue 3). The development and demo are available at: https://github.com/dangvanthanh/orchardcoredev. However, I need to modify the ESbuild configuration for input and output assets. |
Is your feature request related to a problem? Please describe.
Currently, Orchard Core uses Gulp to bundle TypeScript, JavaScript, and CSS. However, Gulp is no longer being developed for new features.
Describe the solution you'd like
I was develop some project using Orchard Core. I use TypeScript and TailwindCSS for CSS. So I migrate Gulp to ESBuild. It's fast, fully support TypeScript, tree-shaking, CSS modules...
Describe alternatives you've considered
I am considering the possibility that Orchard Core has plans to use ESBuild instead of Gulp.
The text was updated successfully, but these errors were encountered: