-
Notifications
You must be signed in to change notification settings - Fork 3
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
fix(deps): update all dependencies #21
Open
renovate
wants to merge
1
commit into
main
Choose a base branch
from
renovate/all
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
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
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
renovate
bot
changed the title
chore(deps): update all dependencies to v6.18.1
chore(deps): update all dependencies
Jan 12, 2024
renovate
bot
force-pushed
the
renovate/all
branch
from
January 12, 2024 15:46
396e3e4
to
0260bd6
Compare
Deploying natainditama with Cloudflare Pages
|
renovate
bot
force-pushed
the
renovate/all
branch
from
January 13, 2024 03:48
0260bd6
to
79d3b11
Compare
renovate
bot
force-pushed
the
renovate/all
branch
from
January 14, 2024 06:35
79d3b11
to
c42cd11
Compare
renovate
bot
force-pushed
the
renovate/all
branch
from
January 15, 2024 16:52
c42cd11
to
83b2572
Compare
renovate
bot
force-pushed
the
renovate/all
branch
from
January 15, 2024 21:03
83b2572
to
bace690
Compare
renovate
bot
force-pushed
the
renovate/all
branch
from
January 17, 2024 05:30
bace690
to
1105664
Compare
renovate
bot
force-pushed
the
renovate/all
branch
from
January 18, 2024 07:01
1105664
to
023a298
Compare
renovate
bot
force-pushed
the
renovate/all
branch
from
January 18, 2024 11:50
023a298
to
dfc0027
Compare
renovate
bot
force-pushed
the
renovate/all
branch
from
January 18, 2024 17:40
dfc0027
to
911fa19
Compare
renovate
bot
force-pushed
the
renovate/all
branch
from
January 19, 2024 02:06
911fa19
to
9ebd0a3
Compare
renovate
bot
force-pushed
the
renovate/all
branch
from
January 19, 2024 11:21
9ebd0a3
to
7a455d6
Compare
renovate
bot
force-pushed
the
renovate/all
branch
from
January 20, 2024 04:42
7a455d6
to
1dcddae
Compare
renovate
bot
force-pushed
the
renovate/all
branch
from
January 20, 2024 10:56
1dcddae
to
0c55c41
Compare
renovate
bot
force-pushed
the
renovate/all
branch
from
December 16, 2024 04:16
16fb365
to
c22d096
Compare
renovate
bot
force-pushed
the
renovate/all
branch
from
December 20, 2024 23:26
c22d096
to
5800b3d
Compare
renovate
bot
force-pushed
the
renovate/all
branch
from
December 26, 2024 19:40
5800b3d
to
8f7b36e
Compare
renovate
bot
force-pushed
the
renovate/all
branch
from
December 31, 2024 13:53
8f7b36e
to
a429598
Compare
renovate
bot
force-pushed
the
renovate/all
branch
from
January 11, 2025 21:07
a429598
to
271b3f8
Compare
renovate
bot
force-pushed
the
renovate/all
branch
from
January 16, 2025 20:26
271b3f8
to
3f93845
Compare
renovate
bot
force-pushed
the
renovate/all
branch
from
January 17, 2025 12:11
3f93845
to
e10bd2e
Compare
renovate
bot
force-pushed
the
renovate/all
branch
from
January 19, 2025 09:03
e10bd2e
to
cd0924c
Compare
renovate
bot
force-pushed
the
renovate/all
branch
from
January 19, 2025 20:56
cd0924c
to
f2e674e
Compare
renovate
bot
force-pushed
the
renovate/all
branch
from
January 22, 2025 02:00
f2e674e
to
ddd96a9
Compare
renovate
bot
force-pushed
the
renovate/all
branch
from
January 23, 2025 18:18
ddd96a9
to
df9d1e8
Compare
renovate
bot
force-pushed
the
renovate/all
branch
from
January 24, 2025 21:51
df9d1e8
to
88295e9
Compare
renovate
bot
force-pushed
the
renovate/all
branch
from
January 26, 2025 13:56
88295e9
to
2b0bff3
Compare
renovate
bot
force-pushed
the
renovate/all
branch
from
January 29, 2025 16:47
2b0bff3
to
9afd3a9
Compare
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:
1.3.0
->1.3.2
1.0.2
->1.1.1
10.4.16
->10.4.20
0.7.0
->0.7.1
2.1.0
->2.1.1
3.6.1
->3.7.0
2.29.1
->2.31.0
5.1.2
->5.2.3
15.2.0
->15.4.3
8.4.33
->8.5.1
3.1.1
->3.4.2
2.2.0
->2.6.0
5.3.3
->5.7.3
Release Notes
radix-ui/primitives (@radix-ui/react-slot)
v1.1.1
Compare Source
v1.1.0
postcss/autoprefixer (autoprefixer)
v10.4.20
Compare Source
fit-content
prefix for Firefox.v10.4.19
Compare Source
end value has mixed support, consider using flex-end
warningsince
end
/start
now have good support.v10.4.18
Compare Source
-webkit-box-orient
on-webkit-line-clamp
(@Goodwine).v10.4.17
Compare Source
user-select: contain
prefixes.joe-bell/cva (class-variance-authority)
v0.7.1
Compare Source
What's Changed
New Contributors
Full Changelog: joe-bell/cva@v0.7.0...v0.7.1
lukeed/clsx (clsx)
v2.1.1
Compare Source
Patches
bigint
inClassValue
type: (#96):3d960ab
Accommodates recent
@types/react
changes toReactNode
.Thank you @ViliamKopecky~!
Chores
licenses.dev
badge:684509c
This service recursively analyzes entire dependency graphs to ensure that a package (or your project) is using permissive licenses. For example, here's a results table for
polka@next
and a largerastro
example.import-js/eslint-import-resolver-typescript (eslint-import-resolver-typescript)
v3.7.0
Compare Source
Minor Changes
#326
93ea130
Thanks @SukkaW! - This version has implemented theeslint-plugin-import-x
's v3 resolver interface. This allows you to use import/require to referenceeslint-import-resolver-typescript
directly in your ESLint flat config:Previously
Now
Note that this only works with
eslint-plugin-import-x@>=4.5.0
. You can't usecreateTypeScriptImportResolver
with the older versions ofeslint-plugin-import-x
or any existing versions ofeslint-plugin-import
.v3.6.3
Compare Source
Patch Changes
#305
f8d7b82
Thanks @SukkaW! - Fix resolve fornode:test
,node:sea
, andnode:sqlite
without sacrificing installation size#288
a4c6c78
Thanks @SunsetTechuila! - fix: ignore bun built-in modulesimport-js/eslint-plugin-import (eslint-plugin-import)
v2.31.0
Compare Source
Added
order
]: allow validating named imports ([#3043], thanks [@manuth])extensions
]: add thecheckTypeImports
option ([#2817], thanks [@phryneas])Fixed
ExportMap
/ flat config: includelanguageOptions
in context ([#3052], thanks [@michaelfaith])no-named-as-default
]: Allow using an identifier if the export is both a named and a default export ([#3032], thanks [@akwodkiewicz])export
]: False positive for exported overloaded functions in TS ([#3065], thanks [@liuxingbaoyu])exportMap
: export map cache is tainted by unreliable parse results ([#3062], thanks [@michaelfaith])exportMap
: improve cacheKey when using flat config ([#3072], thanks [@michaelfaith])Changed
no-relative-packages
]: fix typo ([#3066], thanks [@joshuaobrien])no-cycle
]: dont scc for each linted file ([#3068], thanks [@soryy708])no-cycle
]: adddisableScc
to docs ([#3070], thanks [@soryy708])RuleTester
([#3071], thanks [@G-Rath])no-restricted-paths
]: fix grammar ([#3073], thanks [@unbeauvoyage])no-default-export
], [no-named-export
]: add test case (thanks [@G-Rath])v2.30.0
Compare Source
Added
dynamic-import-chunkname
]: addallowEmpty
option to allow empty leading comments ([#2942], thanks [@JiangWeixian])dynamic-import-chunkname
]: Allow empty chunk name when webpackMode: 'eager' is set; add suggestions to remove name in eager mode ([#3004], thanks [@amsardesai])no-unused-modules
]: AddignoreUnusedTypeExports
option ([#3011], thanks [@silverwind])Fixed
no-extraneous-dependencies
]: allow wrong path ([#3012], thanks [@chabb])no-cycle
]: use scc algorithm to optimize ([#2998], thanks [@soryy708])no-duplicates
]: Removing duplicates breaks in TypeScript ([#3033], thanks [@yesl-kim])newline-after-import
]: fix considerComments option when require ([#2952], thanks [@developer-bandi])order
]: do not compare first path segment for relative paths ([#2682]) ([#2885], thanks [@mihkeleidast])Changed
no-extraneous-dependencies
: Make glob pattern description more explicit ([#2944], thanks [@mulztob])no-unused-modules
]: add console message to help debug [#2866]ExportMap
: make procedures static instead of monkeypatching exportmap ([#2982], thanks [@soryy708])ExportMap
: separate ExportMap instance from its builder logic ([#2985], thanks [@soryy708])order
: Add a quick note on how unbound imports and --fix ([#2640], thanks [@minervabot])exportMapBuilder
: avoid hoisting ([#2989], thanks [@soryy708])ExportMap
: extract "builder" logic to separate files ([#2991], thanks [@soryy708])order
]: update the description of thepathGroupsExcludedImportTypes
option ([#3036], thanks [@liby])prettier/eslint-plugin-prettier (eslint-plugin-prettier)
v5.2.3
Compare Source
Patch Changes
9c6141f
Thanks @BPScott! - Add name field to recommended flat configv5.2.2
Compare Source
Patch Changes
aa5b59f
Thanks @ntnyq! - fix: report node when loc not foundv5.2.1
Compare Source
Patch Changes
ac036cc
Thanks @OrlovAlexei! - build(deps): Bump synckit from 0.8.6 to 0.9.1v5.1.3
Compare Source
Patch Changes
985b33c
Thanks @JounQin! - chore: addpackage.json
intoexports
maplint-staged/lint-staged (lint-staged)
v15.4.3
Compare Source
Patch Changes
cbfed1d
Thanks @tarik02! - Adjust TypeScript types for the default export so that it can be used as a value without error TS2693.v15.4.2
Compare Source
Patch Changes
8827ebf
Thanks @iiroj! - Change lint-staged's dependencies to use caret (^
) ranges instead of tilde (~
). This makes it easier for package managers to perform dependency management when minor-level updates are also permitted instead of just patch-level.v15.4.1
Compare Source
Patch Changes
#1504
1c7a45e
Thanks @iiroj! - Default TypeScript config filenames match JS equivalents.#1504
9cc18c9
Thanks @iiroj! - Add missing conditional exports syntax for TypeScript types.v15.4.0
Compare Source
Minor Changes
#1500
a8ec1dd
Thanks @iiroj! - Lint-staged now provides TypeScript types for the configuration and main Node.js API. You can use the JSDoc syntax in your JS configuration files:It's also possible to use the
.ts
file extension for the configuration if your Node.js version supports it. The--experimental-strip-types
flag was introduced in Node.js v22.6.0 and unflagged in v23.6.0, enabling Node.js to execute TypeScript files without additional configuration.Patch Changes
9b79364
Thanks @iiroj! - Handle possible failures when logging user shell for debug info.v15.3.0
Compare Source
Minor Changes
#1495
e69da9e
Thanks @iiroj! - Added more info to the debug logs so that "environment" info doesn't need to be added separately to GitHub issues.#1493
fa0fe98
Thanks @iiroj! - Added more help messages around the automaticgit stash
that lint-staged creates as a backup (by default). The console output also displays the short git hash of the stash so that it's easier to recover lost files in case some fatal errors are encountered, or the process is killed before completing.For example:
where the backup can be seen with
git show 20addf8
, orgit stash list
:v15.2.11
Compare Source
Patch Changes
#1484
bcfe309
Thanks @wormsik! - Escape paths containing spaces when using the "shell" option.#1487
7dd8caa
Thanks @iiroj! - Do not treat submodule root paths as "staged files". This caused lint-staged to fail to a Git error when only updating the revision of a submodule.v15.2.10
Compare Source
Patch Changes
e3f283b
Thanks @iiroj! - Update minor dependencies, includingmicromatch@~4.0.8
.v15.2.9
Compare Source
Patch Changes
b69ce2d
Thanks @iiroj! - Set the maximum number of event listeners to the number of tasks. This should silence the console warningMaxListenersExceededWarning: Possible EventEmitter memory leak detected
.v15.2.8
Compare Source
Patch Changes
f0480f0
Thanks @iiroj! - In the previous version the nativegit rev-parse --show-toplevel
command was taken into use for resolving the current git repo root. This version switched the--show-toplevel
flag with--show-cdup
, because on Git installed via MSYS2 the former was returning absolute paths that do not work with Node.jschild_process
. The new flag returns a path relative to the working directory, avoiding the issue.The GitHub Actions workflow has been updated to install Git via MSYS2, to ensure better future compatibility; using the default Git binary in the GitHub Actions runner was working correctly even with MSYS2.
v15.2.7
Compare Source
Patch Changes
a51be80
Thanks @iiroj! - In the previous version the nativegit rev-parse --show-toplevel
command was taken into use for resolving the current git repo root. This version drops the--path-format=absolute
option to support earlier git versions since it's also the default behavior. If you are still having trouble, please try upgradinggit
to the latest version.v15.2.6
Compare Source
Patch Changes
119adb2
Thanks @iiroj! - Use native "git rev-parse" commands to determine git repo root directory and the .git config directory, instead of using custom logic. This hopefully makes path resolution more robust on non-POSIX systems.v15.2.5
Compare Source
Patch Changes
#1424
31a1f95
Thanks @iiroj! - Allow approximately equivalent versions of direct dependencies by using the "~" character in the version ranges. This means a more recent patch version of a dependency is allowed if available.#1423
91abea0
Thanks @iiroj! - Improve error logging when failing to read or parse a configuration file#1424
ee43f15
Thanks @iiroj! - Upgrade [email protected]v15.2.4
Compare Source
Patch Changes
4f4537a
Thanks @iiroj! - Fix release issue with previous version; update dependenciesv15.2.2
Compare Source
Patch Changes
fdcdad4
Thanks @iiroj! - Lint-staged no longer tries to load configuration from files that are not checked out. This might happen when using sparse-checkout.v15.2.1
Compare Source
Patch Changes
e4023f6
Thanks @iiroj! - Ignore stdin of spawned commands so that they don't get stuck waiting. Until now, lint-staged has used the default settings to spawn linter commands. This means thestdin
of the spawned commands has accepted input, and essentially gotten stuck waiting. Now thestdin
is ignored and commands will no longer get stuck. If you relied on this behavior, please open a new issue and describe how; the behavior has not been intended.postcss/postcss (postcss)
v8.5.1
Compare Source
v8.5.0
: 8.5 “Duke Alloces”Compare Source
PostCSS 8.5 brought API to work better with non-CSS sources like HTML, Vue.js/Svelte sources or CSS-in-JS.
@romainmenke during his work on Stylelint added
Input#document
in additional toInput#css
.Thanks to Sponsors
This release was possible thanks to our community.
If your company wants to support the sustainability of front-end infrastructure or wants to give some love to PostCSS, you can join our supporters by:
v8.4.49
Compare Source
source.offset
(by @romainmenke).v8.4.48
Compare Source
v8.4.47
Compare Source
v8.4.46
Compare Source
Cannot read properties of undefined (reading 'before')
.v8.4.45
Compare Source
v8.4.44
Compare Source
markClean is not a function
error.v8.4.43
Compare Source
markClean is not a function
error.v8.4.42
Compare Source
v8.4.41
Compare Source
v8.4.40
Compare Source
v8.4.39
Compare Source
CssSyntaxError
types (by @romainmenke).v8.4.38
Compare Source
endIndex: 0
in errors and warnings (by @romainmenke).v8.4.37
Compare Source
original.column are not numbers
error in another case.v8.4.36
Compare Source
original.column are not numbers
error on broken previous source map.v8.4.35
Compare Source
!
innode.parent.nodes
type.undefined
to node adding method to simplify types.v8.4.34
Compare Source
AtRule#nodes
type (by Tim Weißenfels).prettier/prettier (prettier)
v3.4.2
Compare Source
diff
Treat U+30A0 & U+30FB in Katakana Block as CJK (#16796 by @tats-u)
Prettier doesn't treat U+30A0 & U+30FB as Japanese. U+30FB is commonly used in Japanese to represent the delimitation of first and last names of non-Japanese people or “and”. The following “C言語・C++・Go・Rust” means “C language & C++ & Go & Rust” in Japanese.
U+30A0 can be used as the replacement of the
-
in non-Japanese names (e.g. “Saint-Saëns” (Charles Camille Saint-Saëns) can be represented as “サン゠サーンス” in Japanese), but substituted by ASCII hyphen (U+002D) or U+FF1D (full width hyphen) in many cases (e.g. “サン=サーンス” or “サン=サーンス”).Fix comments print on class methods with decorators (#16891 by @fisker)
Fix non-idempotent formatting (#16899 by @seiyab)
This bug fix is not language-specific. You may see similar change in any languages. This fixes regression in 3.4.0 so change caused by it should yield same formatting as 3.3.3.
v3.4.1
Compare Source
diff
Remove unnecessary parentheses around assignment in
v-on
(#16887 by @fisker)<!-- Input --> <template> <button @​click="foo += 2">Click</button> </template> <!-- Prettier 3.4.0 --> <template> <button @​click="(foo += 2)">Click</button> </template> <!-- Prettier 3.4.1 --> <template> <button @​click="foo += 2">Click</button> </template>
v3.4.0
Compare Source
diff
🔗 Release Notes
v3.3.3
Compare Source
diff
Add parentheses for nullish coalescing in ternary (#16391 by @cdignam-segment)
This change adds clarity to operator precedence.
Add parentheses for decorator expressions (#16458 by @y-schneider)
Prevent parentheses around member expressions or tagged template literals from being removed to follow the stricter parsing rules of TypeScript 5.5.
Support
@let
declaration syntax (#16474 by @sosukesuzuki)Adds support for Angular v18
@let
declaration syntax.Please see the following code example. The
@let
declaration allows you to define local variables within the template:For more details, please refer to the excellent blog post by the Angular Team: Introducing @let in Angular.
We also appreciate the Angular Team for kindly answering our questions to implement this feature.
v3.3.2
Compare Source
diff
Fix handlebars path expressions starts with
@
(#16358 by @Princeyadav05)v3.3.1
Compare Source
diff
Preserve empty lines in front matter (#16347 by @fisker)
Preserve explicit language in front matter (#16348 by @fisker)
Avoid line breaks in import attributes (#16349 by @fisker)
v3.3.0
Compare Source
diff
🔗 Release Notes
v3.2.5
Compare Source
diff
Support Angular inline styles as single template literal (#15968 by @sosukesuzuki)
Angular v17 supports single string inline styles.
Unexpected embedded formatting for Angular template (#15969 by @JounQin)
Computed template should not be considered as Angular component template
Use
"json"
parser fortsconfig.json
by default (#16012 by @sosukesuzuki)In v2.3.0, we introduced
"jsonc"
parser which adds trialing comma by default.When adding a new parser we also define how it will be used based on the
linguist-languages
data.tsconfig.json
is a special file used by TypeScript, it uses.json
file extension, but it actually uses the JSON with Comments syntax. However, we found that there are many third-party tools not recognize it correctly because of tConfiguration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.