chore(deps): update dependency esbuild to v0.12.26 #729
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
1 Participants
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: vikunja/frontend#729
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.12.25
->0.12.26
Release Notes
evanw/esbuild
v0.12.26
Compare Source
Add
--analyze
to print information about the bundle (#1568)The
--metafile=
flag tells esbuild to write information about the bundle into the provided metadata file in JSON format. It contains information about the input files and which other files each one imports, as well as the output files and which input files they include. This information is sufficient to answer many questions such as:Previously you had to either write your own code to answer these questions, or use another tool such as https://bundle-buddy.com/esbuild to visualize the data. Starting with this release you can now also use
--analyze
to enable esbuild's built-in visualizer. It looks like this:This tells you what input files were bundled into each output file as well as the final minified size contribution of each input file as well as the percentage of the output file it takes up. You can also enable verbose analysis with
--analyze=verbose
to see why each input file was included (i.e. which files imported it from the entry point file):There is also a JS API for this:
and a Go API:
Note that this is not the only way to visualize this data. If you want a visualization that's different than the information displayed here, you can easily build it yourself using the information in the metafile that is generated with the
--metafile=
flag.Also note that this data is intended for humans, not machines. The specific format of this data may change over time which will likely break any tools that try to parse it. You should not write a tool to parse this data. You should be using the information in the JSON metadata file instead. Everything in this visualization is derived from the JSON metadata so you are not losing out on any information by not using esbuild's output.
Allow
require.resolve
in non-node builds (#1579)With this release, you can now use
require.resolve
in builds when the target platform is set tobrowser
instead ofnode
as long as the functionwindow.require.resolve
exists somehow. This was already possible when the platform isnode
but when the platform isbrowser
, esbuild generates a no-op shimrequire
function for compatibility reasons (e.g. because some code expectstypeof require
must be"function"
even in the browser). The shim previously had a fallback towindow.require
if it exists, but additional properties of therequire
function such asrequire.resolve
were not copied over to the shim. Now the shim function is only used ifwindow.require
is undefined so additional properties such asrequire.resolve
should now work.This change was contributed by @screetBloom.
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.