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

[Encore] [Frontend] Correct "Removes comments from CSS" comparison #20620

Merged
merged 1 commit into from
Feb 6, 2025

Conversation

Kocal
Copy link
Member

@Kocal Kocal commented Feb 5, 2025

Hey!

Following internal discussions about Encore, I came across this page and found incorrect information, Encore can remove comments from CSS by configuring the CssMinimizerPlugin, included with Encore.

On another note, I don't really understand the sentence Can update 3rd party packages. It looks like a comparaison between importmap:require and something that is not a Node.js package manager... right? isn't this comparison biased?

Thanks!

@carsonbot carsonbot added this to the 6.4 milestone Feb 5, 2025
@Kocal Kocal force-pushed the front-end-toolings-adjustments branch from e3926d4 to bed785d Compare February 5, 2025 20:26
@carsonbot carsonbot changed the title [Frontend] Correct "Removes comments from CSS" comparison [Encore] [Frontend] Correct "Removes comments from CSS" comparison Feb 6, 2025
@javiereguiluz javiereguiluz merged commit a61fa43 into symfony:6.4 Feb 6, 2025
3 checks passed
@javiereguiluz
Copy link
Member

Thanks Hugo!

About your question, I know it seems an "unfair" comparison, but at the same time, I think it's important to highlight this difference. With AssetMapper, you install and update packages with AssetMapper utilities ... whereas with Webpack Encore you cannot do that and need external utilities. It's true that AssetMApper doesn't provide a full-featured package-manager, but it's enough for many use cases.

@Kocal Kocal deleted the front-end-toolings-adjustments branch February 6, 2025 07:50
@Kocal
Copy link
Member Author

Kocal commented Feb 6, 2025

Alright, thanks for the clarification Javier! :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants