Skip to content

Disable syn default features in lightningcss-derive #361

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

Merged

Conversation

chinedufn
Copy link
Contributor

This disables the default syn features in lightningcss-derive's
Cargo.toml.

It also removes an unused syn feature.

Related: #357

Verified

This commit was signed with the committer’s verified signature. The key has expired.
chinedufn Chinedu Francis Nwafili
This disables the default syn features in lightningcss-derive's
Cargo.toml.

It also removes an unused syn feature.

Related: parcel-bundler#357
@@ -11,6 +11,6 @@ repository = "https://github.com/parcel-bundler/lightningcss"
proc-macro = true

[dependencies]
syn = { version = "1.0", features = ["extra-traits"] }
syn = { version = "1.0", default-features = false }
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I didn't check how much was saved here.

In the past I've seen a similar change save about 1s of compile time ia0/data-encoding#56 (comment)

@chinedufn chinedufn changed the title Disable syn default features Disable syn default features in lightningcss-derive Dec 13, 2022
@devongovett devongovett merged commit fc3e08a into parcel-bundler:master Dec 14, 2022
@chinedufn chinedufn deleted the syn-no-default-features branch December 14, 2022 11:18
devongovett added a commit that referenced this pull request Jan 4, 2023
devongovett added a commit that referenced this pull request Jan 4, 2023

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
This reverts commit fc3e08a.
@devongovett
Copy link
Member

Unfortunately this seems to have broken cargo build -p lightningcss-derive which runs when publishing the crate. I'm not sure why it isn't broken when building all of lightningcss though - maybe something else is enabling those features. Anyway, I don't think this should make too much difference now that the "visitor" feature flag of lightningcss exists - lightningcss-derive shouldn't get pulled in at all.

@chinedufn
Copy link
Contributor Author

Ah yeah I should've tried to build the crate on its own. Sounds good to me, thanks.

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.

None yet

2 participants