Here's a maintainance release with small things so far.
NOTE: We're also working to release a 4.1 later this summer with CRDT support for rich text editing by providing explicit support for Y.js documents into both Dexie.js and Dexie Cloud (#1926)
#2011 and #2012: bulkPut() of multiple objects with same primary key would result i liveQueries showing multiple results instead of the last entry only (which is the correct result).
PRs:
#2006 requireAuth with options. Now possible to provide requireAuth: {email, otp, otpId} instead of just requireAuth: true. Useful when implementing magic link authentication.
fix: Nested translation resolution between languages uses the fallback language for nested translations 2216 by preserving issue fix "lng is undefined when formatter used in $t( )" 1938
fix: Nested translation resolution between languages uses the fallback language for nested translations 2216 by preserving issue fix "lng is undefined when formatter used in $t( )" 1938
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 your package.json file (recommended) or be using a version range syntax that only accepts patch upgrades such as ^0.22.0 or ~0.22.0. See npm's documentation about semver for more information.
Revert the recent change to avoid bundling dependencies for node (#3819)
This release reverts the recent change in version 0.22.0 that made --packages=external the default behavior with --platform=node. The default is now back to --packages=bundle.
I've just been made aware that Amazon doesn't pin their dependencies in their "AWS CDK" product, which means that whenever esbuild publishes a new release, many people (potentially everyone?) using their SDK around the world instantly starts using it without Amazon checking that it works first. This change in version 0.22.0 happened to break their SDK. I'm amazed that things haven't broken before this point. This revert attempts to avoid these problems for Amazon's customers. Hopefully Amazon will pin their dependencies in the future.
In addition, this is probably a sign that esbuild is used widely enough that it now needs to switch to a more complicated release model. I may have esbuild use a beta channel model for further development.
When transformed, certain whitespace inside JSX elements is ignored completely if it collapses to an empty string. However, the whitespace should only be ignored if the JSX is being transformed, not if it's being preserved. This release fixes a bug where esbuild was previously incorrectly ignoring collapsed whitespace with --jsx=preserve. Here is an example:
// Original code
<Foo>
<Bar />
</Foo>
// Old output (with --jsx=preserve)
<Foo><Bar /></Foo>;
// New output (with --jsx=preserve)
<Foo>
<Bar />
</Foo>;
v0.22.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 your package.json file (recommended) or be using a version range syntax that only accepts patch upgrades such as ^0.21.0 or ~0.21.0. See npm's documentation about semver for more information.
This breaking change is an experiment. People are commonly confused when using esbuild to bundle code for node (i.e. for --platform=node) because some packages may not be intended for bundlers, and may use node-specific features that don't work with a bundler. Even though esbuild's "getting started" instructions say to use --packages=external to work around this problem, many people don't read the documentation and don't do this, and are then confused when it doesn't work. So arguably this is a bad default behavior for esbuild to have if people keep tripping over this.
With this release, esbuild will now omit packages from the bundle by default when the platform is node (i.e. the previous behavior of --packages=external is now the default in this case). Note that your dependencies must now be present on the file system when your bundle is run. If you don't want this behavior, you can do --packages=bundle to allow packages to be included in the bundle (i.e. the previous default behavior). Note that --packages=bundle doesn't mean all packages are bundled, just that packages are allowed to be bundled. You can still exclude individual packages from the bundle using --external: even when --packages=bundle is present.
The --packages= setting considers all import paths that "look like" package imports in the original source code to be package imports. Specifically import paths that don't start with a path segment of / or . or .. are considered to be package imports. The only two exceptions to this rule are subpath imports (which start with a # character) and TypeScript path remappings via paths and/or baseUrl in tsconfig.json (which are applied first).
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 your package.json file (recommended) or be using a version range syntax that only accepts patch upgrades such as ^0.22.0 or ~0.22.0. See npm's documentation about semver for more information.
Revert the recent change to avoid bundling dependencies for node (#3819)
This release reverts the recent change in version 0.22.0 that made --packages=external the default behavior with --platform=node. The default is now back to --packages=bundle.
I've just been made aware that Amazon doesn't pin their dependencies in their "AWS CDK" product, which means that whenever esbuild publishes a new release, many people (potentially everyone?) using their SDK around the world instantly starts using it without Amazon checking that it works first. This change in version 0.22.0 happened to break their SDK. I'm amazed that things haven't broken before this point. This revert attempts to avoid these problems for Amazon's customers. Hopefully Amazon will pin their dependencies in the future.
In addition, this is probably a sign that esbuild is used widely enough that it now needs to switch to a more complicated release model. I may have esbuild use a beta channel model for further development.
When transformed, certain whitespace inside JSX elements is ignored completely if it collapses to an empty string. However, the whitespace should only be ignored if the JSX is being transformed, not if it's being preserved. This release fixes a bug where esbuild was previously incorrectly ignoring collapsed whitespace with --jsx=preserve. Here is an example:
// Original code
<Foo>
<Bar />
</Foo>
// Old output (with --jsx=preserve)
<Foo><Bar /></Foo>;
// New output (with --jsx=preserve)
<Foo>
<Bar />
</Foo>;
0.22.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 your package.json file (recommended) or be using a version range syntax that only accepts patch upgrades such as ^0.21.0 or ~0.21.0. See npm's documentation about semver for more information.
This breaking change is an experiment. People are commonly confused when using esbuild to bundle code for node (i.e. for --platform=node) because some packages may not be intended for bundlers, and may use node-specific features that don't work with a bundler. Even though esbuild's "getting started" instructions say to use --packages=external to work around this problem, many people don't read the documentation and don't do this, and are then confused when it doesn't work. So arguably this is a bad default behavior for esbuild to have if people keep tripping over this.
With this release, esbuild will now omit packages from the bundle by default when the platform is node (i.e. the previous behavior of --packages=external is now the default in this case). Note that your dependencies must now be present on the file system when your bundle is run. If you don't want this behavior, you can do --packages=bundle to allow packages to be included in the bundle (i.e. the previous default behavior). Note that --packages=bundle doesn't mean all packages are bundled, just that packages are allowed to be bundled. You can still exclude individual packages from the bundle using --external: even when --packages=bundle is present.
The --packages= setting considers all import paths that "look like" package imports in the original source code to be package imports. Specifically import paths that don't start with a path segment of / or . or .. are considered to be package imports. The only two exceptions to this rule are subpath imports (which start with a # character) and TypeScript path remappings via paths and/or baseUrl in tsconfig.json (which are applied first).
Declarations that appear after nested rules are deprecated, because the
semantics Sass has historically used are different from the semantics
specified by CSS. In the future, Sass will adopt the standard CSS semantics.
Potentially breaking bug fix:// in certain places such as unknown
at-rule values was being preserved in the CSS output, leading to potentially
invalid CSS. It's now properly parsed as a silent comment and omitted from the
CSS output.
1.77.6
Fix a few cases where comments and occasionally even whitespace wasn't allowed
between the end of Sass statements and the following semicolon.
Commits
be9c3ac Run Windows ARM64 releases on windows-latest instead (#2275)
Most Recent Ignore Conditions Applied to This Pull Request
| Dependency Name | Ignore Conditions |
| --- | --- |
| jsdom | [>= 22.1.a, < 22.2] |
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 ignore conditions` will show all of the ignore conditions of the specified dependency
- `@dependabot ignore major version` will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
- `@dependabot ignore minor version` will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
- `@dependabot ignore ` will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
- `@dependabot unignore ` will remove all of the ignore conditions of the specified dependency
- `@dependabot unignore ` will remove the ignore condition of the specified dependency and ignore conditions
Bumps the external-dependencies group with 13 updates in the / directory:
4.0.74.0.823.11.523.12.26.1.276.1.388.1.08.2.04.4.14.4.30.0.2680.0.2694.3.55.1.420.14.222.1.00.21.50.23.024.1.024.1.16.4.36.4.41.77.51.77.810.4.010.7.3Updates
dexiefrom 4.0.7 to 4.0.8Release notes
Sourced from dexie's releases.
Commits
8191678Build outputbea6a0bMerge remote-tracking branch 'origin/releases'7798fdfReleasing v4.0.8035bd59Cleaned up dep versions in package.jsons (removed -alpha.x as 4.0.x stable ha...2b7d3aeResolve #2011 and #2012 (#2033)df2f963Another reason why #2026 failed - KeyPathValue<string> should evaluate toany.4cfa6ecUse native bigint type instead of BigInt object type4361ca6Resolve issue #2026795f60crequireAuth with options (#2006)d8d8527add complete ./dist/* to package.json exports (#2004)Updates
i18nextfrom 23.11.5 to 23.12.2Release notes
Sourced from i18next's releases.
Changelog
Sourced from i18next's changelog.
Commits
83cfe9c23.12.2357e81ffix: Nested translation resolution between languages uses the fallback langua...1e714a0example: update dependencies4002c1723.12.182f21aanew buildb987d27use explicit imports for utils (#2212)b9ae23923.12.05555dd6feat: Add posibility to override keyPrefix for certain translation. #2211de3b6b7test: update vitest to v2 (#2210)32e8a6btypes: mergehasLoadedNamespacedeclarations (#2209)Updates
tldtsfrom 6.1.27 to 6.1.38Release notes
Sourced from tldts's releases.
... (truncated)
Changelog
Sourced from tldts's changelog.
... (truncated)
Commits
120525cBump version to: v6.1.38 [skip ci]44cbb7dUpdate CHANGELOG.md [skip ci]fa2255cUpdate upstream public suffix list (#2122)5e3e0f9Bump@types/nodefrom 22.0.0 to 22.0.2 (#2119)8b18236Bump rollup from 4.19.1 to 4.19.2 (#2120)cc74b70Bump@typescript-eslint/eslint-pluginfrom 7.17.0 to 7.18.0 (#2118)6a9422dBump version to: v6.1.37 [skip ci]3dbeaadUpdate CHANGELOG.md [skip ci]5a7c936Update upstream public suffix list (#2116)c844326Bump@typescript-eslint/parserfrom 7.17.0 to 7.18.0 (#2117)Updates
web-extfrom 8.1.0 to 8.2.0Release notes
Sourced from web-ext's releases.
Commits
c4471a78.2.0a81ddc1chore(deps): bump addons-linter from 6.30.0 to 6.31.1 (#3175)9bbf2c3chore(deps): bump addons-linter from 6.29.0 to 6.30.0 (#3173)a481853chore(deps): bump jose from 5.4.0 to 5.4.1 (#3174)e433987chore(deps): bump ws from 8.17.0 to 8.17.1 (#3171)6620278chore(deps): bump mkdirp from 1.0.4 to 3.0.1 (#2735)Updates
@fingerprintjs/fingerprintjsfrom 4.4.1 to 4.4.3Release notes
Sourced from
@fingerprintjs/fingerprintjs's releases.Commits
76fca7aBump the version to 4.4.3 (#1018)374aa1cRemove theFeature policy 'Payment' check failed...console error in cross-...b89ae50refactor: MakesuppressUnhandledRejectionWarningreturn the input promise (...fc47f0cBump the version to 4.4.2 (#1015)ec9526bEvent loop releasing optimization (#1014)5e6916aUpdate a vulnerablewsdependency (#1013)366cbd3Bump braces from 3.0.2 to 3.0.3 (#1012)Updates
@types/chromefrom 0.0.268 to 0.0.269Commits
Updates
@types/jasminefrom 4.3.5 to 5.1.4Commits
Updates
@types/nodefrom 20.14.2 to 22.1.0Commits
Updates
esbuildfrom 0.21.5 to 0.23.0Release notes
Sourced from esbuild's releases.
... (truncated)
Changelog
Sourced from esbuild's changelog.
... (truncated)
Commits
9d50680publish 0.23.0 to npmac7fd04Revert "fix #1874: node defaults to--packages=external" (#3820)626ac2cfix #3818: preserve collapsed jsx whitespace7c2eb2ehashbang syntax is part of es202380c6e6epublish 0.22.0 to npm196dcadfix #1874: node defaults to--packages=external3f57db8release notes for #353991663dbProvide API to create a custom esbuild CLI with plugins (#3539)e01c0e0also mention #3665 in release notes65711b3release notes for #3674Updates
globfrom 10.4.1 to 10.4.2Commits
eef7ea310.4.2c76a7d2use package-json-from-dist to look up package.jsonUpdates
jsdomfrom 24.1.0 to 24.1.1Release notes
Sourced from jsdom's releases.
Changelog
Sourced from jsdom's changelog.
Commits
ee8b615Version 24.1.14c167b3Update ESLint to v9c8a5103Update dependencies and dev dependenciesb2235afTrigger selectionchange event on document when selection changesUpdates
karmafrom 6.4.3 to 6.4.4Release notes
Sourced from karma's releases.
Changelog
Sourced from karma's changelog.
Commits
84f85e7chore(release): 6.4.4 [skip ci]a4d1284build(deps-dev): bump ws from 6.2.1 to 6.2.3Updates
sassfrom 1.77.5 to 1.77.8Release notes
Sourced from sass's releases.
Changelog
Sourced from sass's changelog.
Commits
be9c3acRun Windows ARM64 releases on windows-latest instead (#2275)d4b1939Run pub in verbose mode on windows-arm64c96b5e2Fix windows-arm64 release (#2274)7203d65Deprecated mixed declarations (#2267)1edc247Avoid[this]in Dartdoc comments (#2273)a164889Enable AOT build for windows-arm64 (#2270)04b6251Parse silent comments in_interpolatedDeclarationValue()(#2266)860eb5aFix linux-ia32, linux-arm-musl, and windows-arm64 releases (#2265)7aae1e6Fix a bug where comments were incorrectly forbidden in some cases (#2264)cf6f9d0Build AOT releases with native arm64 runners (#2262)Updates
mochafrom 10.4.0 to 10.7.3Release notes
Sourced from mocha's releases.
... (truncated)
Changelog
Sourced from mocha's changelog.
... (truncated)
Commits
d5766c8chore(main): release 10.7.3 (#5195)afd66effix: make release-please build work (#5194)9e0a4bdchore(main): release 10.7.2 (#5192)7e7a2ecchore: fix failing markdown linting (#5193)1ac5b55docs: improve filtering (#5191)1528c42chore(main): release 10.7.1 (#5189)d7013ddfix: crash with --parallel and --retries both enabled (#5173)5c2989fchore: add knip to validate included dependenciesa777fd1ci: automate releases (#5186)ac5574eci: update towindows-latestin actions (#5185)Most Recent Ignore Conditions Applied to This Pull Request
| Dependency Name | Ignore Conditions | | --- | --- | | jsdom | [>= 22.1.a, < 22.2] |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