chore(deps): update dependency esbuild to v0.14.39 #1944
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
2 Participants
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: vikunja/frontend#1944
Loading…
Reference in New Issue
No description provided.
Delete Branch "renovate/esbuild-0.x"
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:
0.14.38
->0.14.39
Release Notes
evanw/esbuild
v0.14.39
Compare Source
Fix code generation for
export default
and/* @​__PURE__ */
call (#2203)The
/* @​__PURE__ */
comment annotation can be added to function calls to indicate that they are side-effect free. These annotations are passed through into the output by esbuild since many JavaScript tools understand them. However, there was an edge case where printing this comment before a function call caused esbuild to fail to parenthesize a function literal because it thought it was no longer at the start of the expression. This problem has been fixed:Preserve
...
before JSX child expressions (#2245)TypeScript 4.5 changed how JSX child expressions that start with
...
are emitted. Previously the...
was omitted but starting with TypeScript 4.5, the...
is now preserved instead. This release updates esbuild to match TypeScript's new output in this case:Note that this behavior is TypeScript-specific. Babel doesn't support the
...
token at all (it gives the error "Spread children are not supported in React").Slightly adjust esbuild's handling of the
browser
field inpackage.json
(#2239)This release changes esbuild's interpretation of
browser
path remapping to fix a regression that was introduced in esbuild version 0.14.21. Browserify has a bug where it incorrectly matches package paths to relative paths in thebrowser
field, and esbuild replicates this bug for compatibility with Browserify. I have a set of tests that I use to verify that esbuild's replication of this Browserify is accurate here: https://github.com/evanw/package-json-browser-tests. However, I was missing a test case and esbuild's behavior diverges from Browserify in this case. This release now handles this edge case as well:entry.js
:node_modules/pkg/package.json
:node_modules/pkg/sub/foo.js
:node_modules/sub/index.js
:The import path
sub
inrequire('sub')
was previously matching the remapping"./sub/sub.js": "./sub/foo.js"
but with this release it should now no longer match that remapping. Nowrequire('sub')
will only match the remapping"./sub/sub": "./sub/foo.js"
(without the trailing.js
). Browserify apparently only matches without the.js
suffix here.Configuration
📅 Schedule: 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.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Renovate Bot.
Hi renovate!
Thank you for creating a PR!
I've deployed the changes of this PR on a preview environment under this URL: https://1944-renovate-esbuild-0-x--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!