chore(deps): update dev-dependencies #3856
No reviewers
Labels
No Label
area/internal-code
changes requested
confirmed
dependencies
duplicate
good first issue
help wanted
hosting
invalid
kind/bug
kind/feature
question
wontfix
No Milestone
No project
No Assignees
3 Participants
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: vikunja/frontend#3856
Loading…
Reference in New Issue
No description provided.
Delete Branch "renovate/dev-dependencies"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
1.6.0
->1.6.1
20.10.4
->20.10.5
6.14.0
->6.15.0
6.14.0
->6.15.0
0.4.0
->0.5.1
6.0.0
->6.0.1
0.19.9
->0.19.10
8.55.0
->8.56.0
8.0.0
->8.0.1
4.9.0
->4.9.1
5.0.8
->5.0.10
Release Notes
microsoft/rushstack (@rushstack/eslint-patch)
v1.6.1
Compare Source
typescript-eslint/typescript-eslint (@typescript-eslint/eslint-plugin)
v6.15.0
Compare Source
Features
You can read about our versioning strategy and releases on our website.
typescript-eslint/typescript-eslint (@typescript-eslint/parser)
v6.15.0
Compare Source
Note: Version bump only for package @typescript-eslint/parser
You can read about our versioning strategy and releases on our website.
vuejs/tsconfig (@vue/tsconfig)
v0.5.1
Compare Source
v0.5.0
Compare Source
csstools/postcss-plugins (css-has-pseudo)
v6.0.1
Compare Source
December 15, 2023
@csstools/selector-specificity
to3.0.1
(patch)evanw/esbuild (esbuild)
v0.19.10
Compare Source
Fix glob imports in TypeScript files (#3319)
This release fixes a problem where bundling a TypeScript file containing a glob import could emit a call to a helper function that doesn't exist. The problem happened because esbuild's TypeScript transformation removes unused imports (which is required for correctness, as they may be type-only imports) and esbuild's glob import transformation wasn't correctly marking the imported helper function as used. This wasn't caught earlier because most of esbuild's glob import tests were written in JavaScript, not in TypeScript.
Fix
require()
glob imports with bundling disabled (#3546)Previously
require()
calls containing glob imports were incorrectly transformed when bundling was disabled. All glob imports should only be transformed when bundling is enabled. This bug has been fixed.Fix a panic when transforming optional chaining with
define
(#3551, #3554)This release fixes a case where esbuild could crash with a panic, which was triggered by using
define
to replace an expression containing an optional chain. Here is an example:This fix was contributed by @hi-ogawa.
Work around a bug in node's CommonJS export name detector (#3544)
The export names of a CommonJS module are dynamically-determined at run time because CommonJS exports are properties on a mutable object. But the export names of an ES module are statically-determined at module instantiation time by using
import
andexport
syntax and cannot be changed at run time.When you import a CommonJS module into an ES module in node, node scans over the source code to attempt to detect the set of export names that the CommonJS module will end up using. That statically-determined set of names is used as the set of names that the ES module is allowed to import at module instantiation time. However, this scan appears to have bugs (or at least, can cause false positives) because it doesn't appear to do any scope analysis. Node will incorrectly consider the module to export something even if the assignment is done to a local variable instead of to the module-level
exports
object. For example:You can see that node incorrectly thinks the file
confuseNode.js
has an export callednotAnExport
when that file is loaded in an ES module context:To avoid this, esbuild will now rename local variables that use the names
exports
andmodule
when generating CommonJS output for thenode
platform.Fix the return value of esbuild's
super()
shim (#3538)Some people write
constructor
methods that use the return value ofsuper()
instead of usingthis
. This isn't too common because TypeScript doesn't let you do that but it can come up when writing JavaScript. Previously esbuild's class lowering transform incorrectly transformed the return value ofsuper()
intoundefined
. With this release, the return value ofsuper()
will now bethis
instead:Terminate the Go GC when esbuild's
stop()
API is called (#3552)If you use esbuild with WebAssembly and pass the
worker: false
flag toesbuild.initialize()
, then esbuild will run the WebAssembly module on the main thread. If you do this within a Deno test and that test callsesbuild.stop()
to clean up esbuild's resources, Deno may complain that asetTimeout()
call lasted past the end of the test. This happens when the Go is in the middle of a garbage collection pass and has scheduled additional ongoing garbage collection work. Normally callingesbuild.stop()
will terminate the web worker that the WebAssembly module runs in, which will terminate the Go GC, but that doesn't happen if you disable the web worker withworker: false
.With this release, esbuild will now attempt to terminate the Go GC in this edge case by calling
clearTimeout()
on these pending timeouts.Apply
/* @​__NO_SIDE_EFFECTS__ */
on tagged template literals (#3511)Tagged template literals that reference functions annotated with a
@__NO_SIDE_EFFECTS__
comment are now able to be removed via tree-shaking if the result is unused. This is a convention from Rollup. Here is an example:Note that this feature currently only works within a single file, so it's not especially useful. This feature does not yet work across separate files. I still recommend using
@__PURE__
annotations instead of this feature, as they have wider tooling support. The drawback of course is that@__PURE__
annotations need to be added at each call site, not at the declaration, and for non-call expressions such as template literals you need to wrap the expression in an IIFE (immediately-invoked function expression) to create a call expression to apply the@__PURE__
annotation to.Publish builds for IBM AIX PowerPC 64-bit (#3549)
This release publishes a binary executable to npm for IBM AIX PowerPC 64-bit, which means that in theory esbuild can now be installed in that environment with
npm install esbuild
. This hasn't actually been tested yet. If you have access to such a system, it would be helpful to confirm whether or not doing this actually works.eslint/eslint (eslint)
v8.56.0
Compare Source
Features
0dd9704
feat: Support custom severity when reporting unused disable directives (#17212) (Bryan Mishkin)31a7e3f
feat: fix no-restricted-properties false negatives with unknown objects (#17818) (Arka Pratim Chaudhuri)Bug Fixes
7d5e5f6
fix:TypeError: fs.exists is not a function
on read-only file system (#17846) (Francesco Trotta)74739c8
fix: suggestion with invalid syntax in no-promise-executor-return rule (#17812) (Bryan Mishkin)Documentation
9007719
docs: update link in ways-to-extend.md (#17839) (Amel SELMANE)3a22236
docs: Update README (GitHub Actions Bot)54c3ca6
docs: fix migration-guide example (#17829) (Tanuj Kanti)4391b71
docs: check config comments in rule examples (#17815) (Francesco Trotta)fd28363
docs: remove mention about ESLint stylistic rules in readme (#17810) (Zwyx)48ed5a6
docs: Update README (GitHub Actions Bot)Chores
ba6af85
chore: upgrade @eslint/js@8.56.0 (#17864) (Milos Djermanovic)60a531a
chore: package.json update for @eslint/js release (Jenkins)ba87a06
chore: update dependency markdownlint to ^0.32.0 (#17783) (renovate[bot])9271d10
chore: add GitHub issue template for docs issues (#17845) (Josh Goldberg ✨)70a686b
chore: Convert rule tests to FlatRuleTester (#17819) (Nicholas C. Zakas)f3a599d
chore: upgrade eslint-plugin-unicorn to v49.0.0 (#17837) (唯然)905d4b7
chore: upgrade eslint-plugin-eslint-plugin v5.2.1 (#17838) (唯然)4d7c3ce
chore: update eslint-plugin-n v16.4.0 (#17836) (唯然)fd0c60c
ci: unpin Node.js 21.2.0 (#17821) (Francesco Trotta)csstools/postcss-plugins (postcss-focus-within)
v8.0.1
Compare Source
December 15, 2023
rollup/rollup (rollup)
v4.9.1
Compare Source
2023-12-17
Bug Fixes
Pull Requests
vitejs/vite (vite)
v5.0.10
Compare Source
v5.0.9
Compare Source
import.meta
correctly for IIFE worker (#15321) (08d093c), closes #15321Configuration
📅 Schedule: Branch creation - "before 4am" (UTC), 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 has been generated by Renovate Bot.
ac51310fa7
to3795c925d8
chore(deps): update dependency vite to v5.0.9to chore(deps): update dev-dependencies3795c925d8
to1e95a145b1
1e95a145b1
toecd1693db1
ecd1693db1
tocc8e525ac1
cc8e525ac1
to74eca11ffb
74eca11ffb
toc802b8ea85
c802b8ea85
tobfb83974bd
bfb83974bd
to76eae27864
76eae27864
tod2d748e06f
d2d748e06f
to8a251e2372
Edited/Blocked Notification
Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.
You can manually request rebase by checking the rebase/retry box above.
⚠ Warning: custom changes will be lost.
Hi renovate!
Thank you for creating a PR!
I've deployed the changes of this PR on a preview environment under this URL: https://3856-renovate-dev-dependencies--vikunja-frontend-preview.netlify.app
You can use this url to view the changes live and test them out.
You will need to manually connect this to an api running somehwere. The easiest to use is https://try.vikunja.io/.
Have a nice day!