Skip to content
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

Native esbuild integration, defaults switched to esbuild/postcss #461

Merged
merged 23 commits into from
Jan 10, 2022

Conversation

jaredcwhite
Copy link
Member

@jaredcwhite jaredcwhite commented Nov 25, 2021

Resolves #94

BIG CHANGE: after some reflection, I asked myself why—in a world where esbuild and PostCSS are good to go—would we continue to ship with Webpack and Sass as the default? I wouldn't use those as my defaults for any new projects. So this PR switches gears and now esbuild+PostCSS is the default, and you can optionally choose Webpack instead and also optionally choose Sass. This feels right for the year 2022. Sass is opinionated and only necessary if you know why you need it. Same thing for Webpack as well IMHO.

If I hear strong feedback to the contrary, always open to changing my mind. 🙂


  • Tests
  • Documentation (included in the upcoming refreshed website off-repo)
  • Bundled configurations updated to work within the new paradigm (Tailwind & Stimulus)
  • Ensure latest PostCSS version is used in various package.json/scripts

@render
Copy link

render bot commented Nov 25, 2021

@render
Copy link

render bot commented Nov 25, 2021

@jaredcwhite jaredcwhite merged commit dd004e0 into main Jan 10, 2022
@jaredcwhite jaredcwhite deleted the esbuild-bundling branch January 10, 2022 18:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

feat: add the option to use esbuild
1 participant