chore(deps): update dependency esbuild to v0.14.2 #1139
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#1139
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.1
->0.14.2
Release Notes
evanw/esbuild
v0.14.2
Compare Source
Add
[ext]
placeholder for path templates (#1799)This release adds the
[ext]
placeholder to the--entry-names=
,--chunk-names=
, and--asset-names=
configuration options. The[ext]
placeholder takes the value of the file extension without the leading.
, and can be used to place output files with different file extensions into different folders. For example,--asset-names=assets/[ext]/[name]-[hash]
might generate an output path ofassets/png/image-LSAMBFUD.png
.This feature was contributed by @LukeSheard.
Disable star-to-clause transform for external imports (#1801)
When bundling is enabled, esbuild automatically transforms
import * as x from 'y'; x.z()
intoimport {z} as 'y'; z()
to improve tree shaking. This avoids needing to create the import namespace objectx
if it's unnecessary, which can result in the removal of large amounts of unused code. However, this transform shouldn't be done for external imports because that incorrectly changes the semantics of the import. If the exportz
doesn't exist in the previous example, the valuex.z
is a property access that is undefined at run-time, but the valuez
is an import error that will prevent the code from running entirely. This release fixes the problem by avoiding doing this transform for external imports:Disable
calc()
transform for numbers with many fractional digits (#1821)Version 0.13.12 introduced simplification of
calc()
expressions in CSS when minifying. For example,calc(100% / 4)
turns into25%
. However, this is problematic for numbers with many fractional digits because either the number is printed with reduced precision, which is inaccurate, or the number is printed with full precision, which could be longer than the original expression. For example, turningcalc(100% / 3)
into33.33333%
is inaccurate and turning it into33.333333333333336%
likely isn't desired. In this release, minification ofcalc()
is now disabled when any number in the result cannot be represented to full precision with at most five fractional digits.Fix an edge case with
catch
scope handling (#1812)This release fixes a subtle edge case with
catch
scope and destructuring assignment. Identifiers in computed properties and/or default values inside the destructuring binding pattern should reference the outer scope, not the inner scope. The fix was to split the destructuring pattern into its own scope, separate from thecatch
body. Here's an example of code that was affected by this edge case:Go 1.17.2 was upgraded to Go 1.17.4
The previous release was built with Go 1.17.2, but this release is built with Go 1.17.4. This is just a routine upgrade. There are no changes significant to esbuild outside of some security-related fixes to Go's HTTP stack (but you shouldn't be running esbuild's dev server in production anyway).
One notable change related to this is that esbuild's publishing script now ensures that git's state is free of uncommitted and/or untracked files before building. Previously this wasn't the case because publishing esbuild involved changing the version number, running the publishing script, and committing at the end, which meant that files were uncommitted during the build process. I also typically had some untracked test files in the same directory during publishing (which is harmless).
This matters because there's an upcoming change in Go 1.18 where the Go compiler will include metadata about whether there are untracked files or not when doing a build: https://github.com/golang/go/issues/37475. Changing esbuild's publishing script should mean that when esbuild upgrades to Go 1.18, esbuild's binary executables will be marked as being built off of a specific commit without any modifications. This is important for reproducibility. Checking out a specific esbuild commit and building it should give a bitwise-identical binary executable to one that I published. But if this metadata indicated that there were untracked files during the published build, then the resulting executable would no longer be bitwise-identical.
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://1139-renovateesbuild-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!
4ef65d8713
to47d58d9388