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

Upgrade lilconfig version to enable ESM support #14029

Closed

Conversation

thibautsabot
Copy link

This PR #12455 was merged last year by a lilconfig maintainer.

However, looking at the merge commit here, only the package-lock.json file was changed, the package.json didn't make it through.

Upgrading to lilconfig v3 allows user to use ESM for importing postcss configs.
(For example, when using "type": "module" in package.json)

On this branch, I used the latest version (which includes security patches), alongside a small bump to postcss-load-config.

@TomTom-Labs
Copy link

Can I bring this Pull Request up the stack again?

@hosemadev
Copy link

Also, upgrading this, would resolve:

"Versions of the package lilconfig from 3.1.0 and before 3.1.1 are vulnerable to Arbitrary Code Execution due to the insecure usage of eval in the dynamicImport function."

@shellscape
Copy link

Can we please get this merged? This resolves an error with my project as reported here shellscape/jsx-email#257

@shellscape
Copy link

@thibautsabot lilconfig@3.1.3 was just released today that contains an important fix for windows absolute paths.

@thecrypticace thecrypticace requested a review from a team as a code owner December 3, 2024 19:05
thecrypticace added a commit that referenced this pull request Dec 3, 2024
This PR updates `lilconfig` from v2.1.0 to v3.1.3. Significant
improvements to this package include Windows absolute path support as
well as ESM config files support. This supersedes
#14029 which has fallen
behind and has conflicts with the upstream branch. This is a critical
update for Next.js apps running in development which have dependencies
on packages that use an updated version of `lilconfig`. I understand
that v4 will not be using `lilconfig` but it's an important update for
users on v3.x in the meantime.

---------

Co-authored-by: Jordan Pittman <jordan@cryptica.me>
@thecrypticace
Copy link
Contributor

Closing in favor of #15289

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.

5 participants