Bump esbuild, @vitejs/plugin-react and vite in /farmasia-ui
Bumps esbuild to 0.25.1 and updates ancestor dependencies esbuild, @vitejs/plugin-react and vite. These dependencies need to be updated together.
Updates esbuild
from 0.21.5 to 0.25.1
Release notes
Sourced from esbuild's releases.
v0.25.1
Fix incorrect paths in inline source maps (#4070, #4075, #4105)
This fixes a regression from version 0.25.0 where esbuild didn't correctly resolve relative paths contained within source maps in inline
sourceMappingURL
data URLs. The paths were incorrectly being passed through as-is instead of being resolved relative to the source file containing thesourceMappingURL
comment, which was due to the data URL not being a file URL. This regression has been fixed, and this case now has test coverage.Fix invalid generated source maps (#4080, #4082, #4104, #4107)
This release fixes a regression from version 0.24.1 that could cause esbuild to generate invalid source maps. Specifically under certain conditions, esbuild could generate a mapping with an out-of-bounds source index. It was introduced by code that attempted to improve esbuild's handling of "null" entries in source maps (i.e. mappings with a generated position but no original position). This regression has been fixed.
This fix was contributed by
@jridgewell
.Fix a regression with non-file source map paths (#4078)
The format of paths in source maps that aren't in the
file
namespace was unintentionally changed in version 0.25.0. Path namespaces is an esbuild-specific concept that is optionally available for plugins to use to distinguish paths fromfile
paths and from paths meant for other plugins. Previously the namespace was prepended to the path joined with a:
character, but version 0.25.0 unintentionally failed to prepend the namespace. The previous behavior has been restored.Fix a crash with
switch
optimization (#4088)The new code in the previous release to optimize dead code in switch statements accidentally introduced a crash in the edge case where one or more switch case values include a function expression. This is because esbuild now visits the case values first to determine whether any cases are dead code, and then visits the case bodies once the dead code status is known. That triggered some internal asserts that guard against traversing the AST in an unexpected order. This crash has been fixed by changing esbuild to expect the new traversal ordering. Here's an example of affected code:
switch (x) { case '': return y.map(z => z.value) case y.map(z => z.key).join(','): return [] }
Update Go from 1.23.5 to 1.23.7 (#4076, #4077)
This should have no effect on existing code as this version change does not change Go's operating system support. It may remove certain reports from vulnerability scanners that detect which version of the Go compiler esbuild uses.
This PR was contributed by
@MikeWillCook
.v0.25.0
This release deliberately contains backwards-incompatible changes. To avoid automatically picking up releases like this, you should either be pinning the exact version of
esbuild
in yourpackage.json
file (recommended) or be using a version range syntax that only accepts patch upgrades such as^0.24.0
or~0.24.0
. See npm's documentation about semver for more information.
Restrict access to esbuild's development server (GHSA-67mh-4wv8-2f99)
This change addresses esbuild's first security vulnerability report. Previously esbuild set the
Access-Control-Allow-Origin
header to*
to allow esbuild's development server to be flexible in how it's used for development. However, this allows the websites you visit to make HTTP requests to esbuild's local development server, which gives read-only access to your source code if the website were to fetch your source code's specific URL. You can read more information in the report.Starting with this release, CORS will now be disabled, and requests will now be denied if the host does not match the one provided to
--serve=
. The default host is0.0.0.0
, which refers to all of the IP addresses that represent the local machine (e.g. both127.0.0.1
and192.168.0.1
). If you want to customize anything about esbuild's development server, you can put a proxy in front of esbuild and modify the incoming and/or outgoing requests.In addition, the
serve()
API call has been changed to return an array ofhosts
instead of a singlehost
string. This makes it possible to determine all of the hosts that esbuild's development server will accept.Thanks to
@sapphi-red
for reporting this issue.Delete output files when a build fails in watch mode (#3643)
It has been requested for esbuild to delete files when a build fails in watch mode. Previously esbuild left the old files in place, which could cause people to not immediately realize that the most recent build failed. With this release, esbuild will now delete all output files if a rebuild fails. Fixing the build error and triggering another rebuild will restore all output files again.
... (truncated)
Changelog
Sourced from esbuild's changelog.
Changelog: 2024
This changelog documents all esbuild versions published in the year 2024 (versions 0.19.12 through 0.24.2).
0.24.2
Fix regression with
--define
andimport.meta
(#4010, #4012, #4013)The previous change in version 0.24.1 to use a more expression-like parser for
define
values to allow quoted property names introduced a regression that removed the ability to use--define:import.meta=...
. Even thoughimport
is normally a keyword that can't be used as an identifier, ES modules special-case theimport.meta
expression to behave like an identifier anyway. This change fixes the regression.This fix was contributed by
@sapphi-red
.0.24.1
Allow
es2024
as a target intsconfig.json
(#4004)TypeScript recently added
es2024
as a compilation target, so esbuild now supports this in thetarget
field oftsconfig.json
files, such as in the following configuration file:{ "compilerOptions": { "target": "ES2024" } }
As a reminder, the only thing that esbuild uses this field for is determining whether or not to use legacy TypeScript behavior for class fields. You can read more in the documentation.
This fix was contributed by
@billyjanitsch
.Allow automatic semicolon insertion after
get
/set
This change fixes a grammar bug in the parser that incorrectly treated the following code as a syntax error:
class Foo { get *x() {} set *y() {} }
The above code will be considered valid starting with this release. This change to esbuild follows a similar change to TypeScript which will allow this syntax starting with TypeScript 5.7.
Allow quoted property names in
--define
and--pure
(#4008)The
define
andpure
API options now accept identifier expressions containing quoted property names. Previously all identifiers in the identifier expression had to be bare identifiers. This change now makes--define
and--pure
consistent with--global-name
, which already supported quoted property names. For example, the following is now possible:
... (truncated)
Commits
-
6bfc1c1
publish 0.25.1 to npm -
f9b3952
fix #4078: prepend namespaces to source map paths -
ccf3dd7
add "contributed by" in changelog -
48cd7a9
Update Go from 1.23.5 to 1.23.7 (#4077) -
1f04fa4
fix absolute windows paths in source maps -
9ca03f6
also add test case from #4075 -
2f244c0
add test case from #4104 -
1dde994
fix incorrect test names -
9f008c5
fix #4070:file
namespace forsourceMappingURL
-
cbd5eb8
release notes and tests for #4082 - Additional commits viewable in compare view
Updates @vitejs/plugin-react
from 4.3.3 to 4.3.4
Release notes
Sourced from @vitejs/plugin-react
's releases.
v4.3.4
Add Vite 6 to peerDependencies range
Vite 6 is highly backward compatible, not much to add!
Force Babel to output spec compliant import attributes #386
The default was an old spec (
with type: "json"
). We now enforce spec compliant (with { type: "json" }
)
Changelog
Sourced from @vitejs/plugin-react
's changelog.
4.3.4 (2024-11-26)
Add Vite 6 to peerDependencies range
Vite 6 is highly backward compatible, not much to add!
Force Babel to output spec compliant import attributes #386
The default was an old spec (
with type: "json"
). We now enforce spec compliant (with { type: "json" }
)
Commits
Updates vite
from 5.4.14 to 6.2.2
Release notes
Sourced from vite's releases.
v6.2.2
Please refer to CHANGELOG.md for details.
create-vite@6.2.1
Please refer to CHANGELOG.md for details.
v6.2.1
Please refer to CHANGELOG.md for details.
create-vite@6.2.0
Please refer to CHANGELOG.md for details.
v6.2.0
Please refer to CHANGELOG.md for details.
v6.2.0-beta.1
Please refer to CHANGELOG.md for details.
v6.2.0-beta.0
Please refer to CHANGELOG.md for details.
create-vite@6.1.1
Please refer to CHANGELOG.md for details.
v6.1.1
Please refer to CHANGELOG.md for details.
create-vite@6.1.0
Please refer to CHANGELOG.md for details.
v6.1.0
Please refer to CHANGELOG.md for details.
v6.1.0-beta.2
Please refer to CHANGELOG.md for details.
v6.1.0-beta.1
Please refer to CHANGELOG.md for details.
v6.1.0-beta.0
Please refer to CHANGELOG.md for details.
v6.0.11
Please refer to CHANGELOG.md for details.
v6.0.10
Please refer to CHANGELOG.md for details.
v6.0.9
This version contains a breaking change due to security fixes. See https://github.com/vitejs/vite/security/advisories/GHSA-vg6x-rcgg-rjx6 for more details.
... (truncated)
Changelog
Sourced from vite's changelog.
6.2.2 (2025-03-14)
- fix: await client buildStart on top level buildStart (#19624) (b31faab), closes #19624
- fix(css): inline css correctly for double quote use strict (#19590) (d0aa833), closes #19590
- fix(deps): update all non-major dependencies (#19613) (363d691), closes #19613
- fix(indexHtml): ensure correct URL when querying module graph (#19601) (dc5395a), closes #19601
- fix(preview): use preview https config, not server (#19633) (98b3160), closes #19633
- fix(ssr): use optional chaining to prevent "undefined is not an object" happening in `ssrRewriteStac (4309755), closes #19612
- feat: show friendly error for malformed
base
(#19616) (2476391), closes #19616- feat(worker): show asset filename conflict warning (#19591) (367d968), closes #19591
- chore: extend commit hash correctly when ambigious with a non-commit object (#19600) (89a6287), closes #19600
6.2.1 (2025-03-07)
- refactor: remove
isBuild
check from preAliasPlugin (#19587) (c9e086d), closes #19587- refactor: restore endsWith usage (#19554) (6113a96), closes #19554
- refactor: use
applyToEnvironment
in internal plugins (#19588) (f678442), closes #19588- fix(css): stabilize css module hashes with lightningcss in dev mode (#19481) (92125b4), closes #19481
- fix(deps): update all non-major dependencies (#19555) (f612e0f), closes #19555
- fix(reporter): fix incorrect bundle size calculation with non-ASCII characters (#19561) (437c0ed), closes #19561
- fix(sourcemap): combine sourcemaps with multiple sources without matched source (#18971) (e3f6ae1), closes #18971
- fix(ssr): named export should overwrite export all (#19534) (2fd2fc1), closes #19534
- feat: add
*?url&no-inline
type and warning for.json?inline
/.json?no-inline
(#19566) (c0d3667), closes #19566- test: add glob import test case (#19516) (aa1d807), closes #19516
- test: convert config playground to unit tests (#19568) (c0e68da), closes #19568
- test: convert resolve-config playground to unit tests (#19567) (db5fb48), closes #19567
- perf: flush compile cache after 10s (#19537) (6c8a5a2), closes #19537
- chore(css): move environment destructuring after condition check (#19492) (c9eda23), closes #19492
- chore(html): remove unnecessary value check (#19491) (797959f), closes #19491
6.2.0 (2025-02-25)
- fix(deps): update all non-major dependencies (#19501) (c94c9e0), closes #19501
- fix(worker): string interpolation in dynamic worker options (#19476) (07091a1), closes #19476
- chore: use unicode cross icon instead of x (#19497) (5c70296), closes #19497
6.2.0-beta.1 (2025-02-21)
- fix(css): temporary add
?.
afterthis.getModuleInfo
invite:css-post
(#19478) (12b0b8a), closes #194786.2.0-beta.0 (2025-02-21)
... (truncated)
Commits
-
b12911e
release: v6.2.2 -
98b3160
fix(preview): use preview https config, not server (#19633) -
b31faab
fix: await client buildStart on top level buildStart (#19624) -
dc5395a
fix(indexHtml): ensure correct URL when querying module graph (#19601) -
2476391
feat: show friendly error for malformedbase
(#19616) -
4309755
fix(ssr): use optional chaining to prevent "undefined is not an object" happe... -
363d691
fix(deps): update all non-major dependencies (#19613) -
d0aa833
fix(css): inline css correctly for double quote use strict (#19590) -
367d968
feat(worker): show asset filename conflict warning (#19591) -
89a6287
chore: extend commit hash correctly when ambigious with a non-commit object (... - Additional commits viewable in compare view
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting ``@dependabot rebase
.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
- ``@dependabot
rebase
will rebase this PR - ``@dependabot
recreate
will recreate this PR, overwriting any edits that have been made to it - ``@dependabot
merge
will merge this PR after your CI passes on it - ``@dependabot
squash and merge
will squash and merge this PR after your CI passes on it - ``@dependabot
cancel merge
will cancel a previously requested merge and block automerging - ``@dependabot
reopen
will reopen this PR if it is closed - ``@dependabot
close
will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - ``@dependabot
show <dependency name> ignore conditions
will show all of the ignore conditions of the specified dependency - ``@dependabot
ignore this major version
will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - ``@dependabot
ignore this minor version
will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - ``@dependabot
ignore this dependency
will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) You can disable automated security fix PRs for this repo from the Security Alerts page.