Sourced from @opentelemetry/auto-instrumentations-web's
releases.
instrumentation-redis: v0.36.0
0.36.0 (2024-01-29)
Features
- deps: update otel-js to 1.21.0/0.48.0 (9624486)
Dependencies
- The following workspace dependencies were updated
- devDependencies
@opentelemetry/contrib-test-utilsbumped from ^0.35.1 to ^0.36.0instrumentation-pino: v0.35.0
0.35.0 (2024-01-29)
Features
- Allow configuring pino to log with different keys (#1867) (33b31d0)
- deps: update otel-js to 1.21.0/0.48.0 (9624486)
Dependencies
- The following workspace dependencies were updated
- devDependencies
@opentelemetry/contrib-test-utilsbumped from ^0.35.1 to ^0.36.0instrumentation-nestjs-core: v0.34.0
0.34.0 (2024-01-29)
Features
- deps: update otel-js to 1.21.0/0.48.0 (9624486)
instrumentation-mysql: v0.35.0
0.35.0 (2024-01-29)
Features
- deps: update otel-js to 1.21.0/0.48.0 (9624486)
Dependencies
... (truncated)
f81f8a7
chore: release main (#1539)8d9687d
feat(fastify): Skip update HTTP's span name and update RpcMetadata's
route in...bf25eb1
chore(renovate): change strategy for @opentelemetry/api,
run experimental upd...3139dbf
chore: update renovate.json (#1575)273993b
chore: re-enable instrumentation-fastify unit test on node@18 (#1568)84a2377
fix(deps): update otel core experimental to ^0.41.0 (#1566)ffb45fe
chore(renovate): split patch and minor rules (#1572)8e2f518
feat(express): Skip update HTTP's span name and update RpcMetadata's
route in...774d254
fix(document-load): compatibility issue with
@opentelemetry/sdk-trace-web@1.1...a18b074
docs: document merge reqiurements (#1553)Sourced from esbuild's releases.
v0.20.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
esbuildin yourpackage.jsonfile (recommended) or be using a version range syntax that only accepts patch upgrades such as^0.19.0or~0.19.0. See npm's documentation about semver for more information.This time there is only one breaking change, and it only matters for people using Deno. Deno tests that use esbuild will now fail unless you make the change described below.
Work around API deprecations in Deno 1.40.x (#3609, #3611)
Deno 1.40.0 was just released and introduced run-time warnings about certain APIs that esbuild uses. With this release, esbuild will work around these run-time warnings by using newer APIs if they are present and falling back to the original APIs otherwise. This should avoid the warnings without breaking compatibility with older versions of Deno.
Unfortunately, doing this introduces a breaking change. The newer child process APIs lack a way to synchronously terminate esbuild's child process, so calling
esbuild.stop()from within a Deno test is no longer sufficient to prevent Deno from failing a test that uses esbuild's API (Deno fails tests that create a child process without killing it before the test ends). To work around this, esbuild'sstop()function has been changed to return a promise, and you now have to changeesbuild.stop()toawait esbuild.stop()in all of your Deno tests.Reorder implicit file extensions within
node_modules(#3341, #3608)In version 0.18.0, esbuild changed the behavior of implicit file extensions within
node_modulesdirectories (i.e. in published packages) to prefer.jsover.tseven when the--resolve-extensions=order prefers.tsover.js(which it does by default). However, doing that also accidentally made esbuild prefer.cssover.ts, which caused problems for people that published packages containing both TypeScript and CSS in files with the same name.With this release, esbuild will reorder TypeScript file extensions immediately after the last JavaScript file extensions in the implicit file extension order instead of putting them at the end of the order. Specifically the default implicit file extension order is
.tsx,.ts,.jsx,.js,.css,.jsonwhich used to become.jsx,.js,.css,.json,.tsx,.tsinnode_modulesdirectories. With this release it will now become.jsx,.js,.tsx,.ts,.css,.jsoninstead.Why even rewrite the implicit file extension order at all? One reason is because the
.jsfile is more likely to behave correctly than the.tsfile. The behavior of the.tsfile may depend ontsconfig.jsonand thetsconfig.jsonfile may not even be published, or may useextendsto refer to a basetsconfig.jsonfile that wasn't published. People can get into this situation when they forget to add all.tsfiles to their.npmignorefile before publishing to npm. Picking.jsover.tshelps make it more likely that resulting bundle will behave correctly.v0.19.12
The "preserve" JSX mode now preserves JSX text verbatim (#3605)
The JSX specification deliberately doesn't specify how JSX text is supposed to be interpreted and there is no canonical way to interpret JSX text. Two most popular interpretations are Babel and TypeScript. Yes they are different (esbuild deliberately follows TypeScript by the way).
Previously esbuild normalized text to the TypeScript interpretation when the "preserve" JSX mode is active. However, "preserve" should arguably reproduce the original JSX text verbatim so that whatever JSX transform runs after esbuild is free to interpret it however it wants. So with this release, esbuild will now pass JSX text through unmodified:
// Original code let el = <a href={'/'} title=''"'> some text {foo} more text </a>// Old output (with --loader=jsx --jsx=preserve) let el = <a href="/" title={
'"}> {" some text"} {foo} {"more text "} </a>;// New output (with --loader=jsx --jsx=preserve) let el = <a href={"/"} title=''"'> some text {foo} more text </a>;
Allow JSX elements as JSX attribute values
JSX has an obscure feature where you can use JSX elements in attribute position without surrounding them with
{...}. It looks like this:
... (truncated)
Sourced from esbuild's changelog.
0.20.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
esbuildin yourpackage.jsonfile (recommended) or be using a version range syntax that only accepts patch upgrades such as^0.19.0or~0.19.0. See npm's documentation about semver for more information.This time there is only one breaking change, and it only matters for people using Deno. Deno tests that use esbuild will now fail unless you make the change described below.
Work around API deprecations in Deno 1.40.x (#3609, #3611)
Deno 1.40.0 was just released and introduced run-time warnings about certain APIs that esbuild uses. With this release, esbuild will work around these run-time warnings by using newer APIs if they are present and falling back to the original APIs otherwise. This should avoid the warnings without breaking compatibility with older versions of Deno.
Unfortunately, doing this introduces a breaking change. The newer child process APIs lack a way to synchronously terminate esbuild's child process, so calling
esbuild.stop()from within a Deno test is no longer sufficient to prevent Deno from failing a test that uses esbuild's API (Deno fails tests that create a child process without killing it before the test ends). To work around this, esbuild'sstop()function has been changed to return a promise, and you now have to changeesbuild.stop()toawait esbuild.stop()in all of your Deno tests.Reorder implicit file extensions within
node_modules(#3341, #3608)In version 0.18.0, esbuild changed the behavior of implicit file extensions within
node_modulesdirectories (i.e. in published packages) to prefer.jsover.tseven when the--resolve-extensions=order prefers.tsover.js(which it does by default). However, doing that also accidentally made esbuild prefer.cssover.ts, which caused problems for people that published packages containing both TypeScript and CSS in files with the same name.With this release, esbuild will reorder TypeScript file extensions immediately after the last JavaScript file extensions in the implicit file extension order instead of putting them at the end of the order. Specifically the default implicit file extension order is
.tsx,.ts,.jsx,.js,.css,.jsonwhich used to become.jsx,.js,.css,.json,.tsx,.tsinnode_modulesdirectories. With this release it will now become.jsx,.js,.tsx,.ts,.css,.jsoninstead.Why even rewrite the implicit file extension order at all? One reason is because the
.jsfile is more likely to behave correctly than the.tsfile. The behavior of the.tsfile may depend ontsconfig.jsonand thetsconfig.jsonfile may not even be published, or may useextendsto refer to a basetsconfig.jsonfile that wasn't published. People can get into this situation when they forget to add all.tsfiles to their.npmignorefile before publishing to npm. Picking.jsover.tshelps make it more likely that resulting bundle will behave correctly.0.19.12
The "preserve" JSX mode now preserves JSX text verbatim (#3605)
The JSX specification deliberately doesn't specify how JSX text is supposed to be interpreted and there is no canonical way to interpret JSX text. Two most popular interpretations are Babel and TypeScript. Yes they are different (esbuild deliberately follows TypeScript by the way).
Previously esbuild normalized text to the TypeScript interpretation when the "preserve" JSX mode is active. However, "preserve" should arguably reproduce the original JSX text verbatim so that whatever JSX transform runs after esbuild is free to interpret it however it wants. So with this release, esbuild will now pass JSX text through unmodified:
// Original code let el = <a href={'/'} title=''"'> some text {foo} more text </a>// Old output (with --loader=jsx --jsx=preserve) let el = <a href="/" title={
'"}> {" some text"} {foo} {"more text "} </a>;// New output (with --loader=jsx --jsx=preserve) let el = <a href={"/"} title=''"'> some text {foo} more text </a>;
Allow JSX elements as JSX attribute values
... (truncated)
2af5ccf
publish 0.20.0 to npm0bccf08
fix esbuild/deno-esbuild#5931f87d
work around api deprecations in deno 1.40.x (#3609)
(#3611)22a9cf5
fix #3341,
fix #3608:
sort .ts right after .jsf8ec300
run npm pkg fix as suggested by the npm clid7fd1ad
publish 0.19.12 to npme04a690
fix #3605:
print the original JSX AST unmodifiedf571399
allow jsx elements as jsx attribute valuesa652e73
run make update-compat-table35c0d65
fix #3574:
ts type parser bug with infer + extends