fix(deps): update dependency lilconfig to v3 #2079
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## next #2079 +/- ##
=======================================
Coverage 97.10% 97.10%
=======================================
Files 111 111
Lines 2766 2766
Branches 738 738
=======================================
Hits 2686 2686
Misses 77 77
Partials 3 3 ☔ View full report in Codecov by Sentry. |
size-limit report 📦
|
booc0mtaco
approved these changes
Oct 21, 2024
Merged
booc0mtaco
added a commit
that referenced
this pull request
Nov 6, 2024
## [15.6.0](v15.5.0...v15.6.0) (2024-11-05) [Storybook](https://61313967cde49b003ae2a860-vjslwzpnbl.chromatic.com/) ### Features * **DataTable:** allow for pinning columns ([#2084](#2084)) ([86d7d07](86d7d07)) ### Bug Fixes * **deps:** update dependency lilconfig to v3 ([#2079](#2079)) ([6f720a4](6f720a4)) * **Select:** pull z-index of select options to top ([#2081](#2081)) ([6f73cfb](6f73cfb))
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
^2.1.0->^3.1.2Release Notes
antonk52/lilconfig
v3.1.2: Webpack friendlyCompare Source
The new changes make lilconfig work as expected when a nodejs app is bundled using webpack.
Thanks @CHC383
v3.1.1: Security releaseCompare Source
Due to how typescript compilation works I had to use
eval()to have a dynamic import in project compiled to commonjs in v3.1.0. Eval call introduced a security vulnerability as it was pointed out to me by kind people from Secfault Security. As there is currently no way to make typescript output dynamic import with a commonjs target I migrated the source code to be in javascript. This means that the code in this repository is the code that gets published to npm. The package still includes first party typescript types inindex.d.tsfile that gets published as well. The runtime code now uses TSDoc annotations to maintain type safety.v3.1.0: Support ESM config files (async api only)Compare Source
Lilconfig now supports loading ESM configuration files.
ESM configs can be searched or loaded via async API only.
ESM syntax can be valid in either
.jsand.mjsfiles in projects with"type": "module"inpackage.json.mjsfiles in projects that use commonjsThanks for pushing this feature @marekdedic
v3.0.0: Cache supportCompare Source
BREAKING CHANGES
New
cachefeatureLilconfig now can cache results in between searches within the same nodejs process. If you are reusing the searcher to look up configuration files, you will get much faster configuration lookups.
Otherwise you can disable it in options using the new
cachekeyThis PR has been generated by Renovate Bot.