Update all-packages #141

renovate · 2022-04-04T01:24:09Z

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@sentry/node	`6.18.2` -> `6.19.7`
@types/lodash	`4.14.179` -> `4.14.182`
@types/node	`14.18.12` -> `14.18.16`
@types/supertest	`2.0.11` -> `2.0.12`
nodemailer (source)	`6.7.2` -> `6.7.4`
prettier (source)	`2.5.1` -> `2.6.2`
sqlite3	`5.0.3` -> `5.0.6`
supertest	`6.2.2` -> `6.2.3`
ts-loader	`9.2.7` -> `9.3.0`
tsc-watch	`4.6.0` -> `4.6.2`
tsconfig-paths	`3.13.0` -> `3.14.1`
typeorm	`0.2.45` -> `0.3.6`
typescript (source)	`4.6.2` -> `4.6.4`

Release Notes

getsentry/sentry-javascript

`v6.19.7`

Compare Source

fix(react): Add children prop type to ErrorBoundary component (#4966)
fix(serverless): Re-add missing modules in Node AWS Lambda Layer (#4982)
fix(tracing): Target tracing bundles for side effects (#4955)

Work in this release contributed by @cameronaziz and @kpdecker. Thank you for your contributions!

`v6.19.6`

Compare Source

fix(typing): Fix typing API in CaptureConsle (#4879)

`v6.19.5`

Compare Source

ref(build): Add debug constants in each package individually (#4842)
ref(build): Introduce central build directory to packages with bundles (#4838) (#4854) (#4868)
feat(utils): Introduce getGlobalSingleton helper (#4860)

`v6.19.4`

Compare Source

feat(react): Add React 18 as peer dep (#4819)
ref(build): Add build/types to tarballs and adjust types entry points (#4824)

Work in this release contributed by @MikevPeeren. Thank you for your contribution!

`v6.19.3`

Compare Source

feat(browser): Add new v7 Fetch Transport (#4765)
feat(browser): Add new v7 XHR Transport (#4803)
fix(core): Use correct version of event when tagging normalization (#4780)
fix(core): Stop mangling _experiments (#4807)
feat(node): Add new v7 http/s Transports (#4781)

`v6.19.2`

Compare Source

feat(core): Add new transports to base backend (#4752)
feat(utils): Add isNaN function (#4759)
fix(integrations): Emit ES5 code in ES5 bundles (#4769)
fix(vue): Drop vue-router peerDep (#4764)
ref(core): Reduce inboundfilters bundle size (#4625)
ref(integrations): Make ReportTypes a union type
ref(node): Add source code context when using LinkedErrors (#4753)
ref(utils): Introduce getEnvelopeType helper (#4751)
ref(utils): Split normalization code into separate module (#4760)

`v6.19.1`

Compare Source

This release fixes a bug from 6.19.0 causing type import errors in most JS SDKs.

fix(types): Point to type definitions in dist folder (#4745)

`v6.19.0`

Compare Source

This release makes a change to the data normalization process, limiting the number of entries or properties which will be included in any given array or object to 1000. Previously there was no limit, so in rare cases you may notice a change in your context data. If this is a problem, you can increase the limit with the new maxNormalizationBreadth setting. See #4689 for details.

feat(build): Create debug versions of minified bundles (#4699)
feat(integrations): Make ES6 integration bundles (#4718)
feat(utils): Limit normalize maximum properties/elements (#4689)
feat(various): Apply debug guard to logger everywhere (#4698)
fix(browser): Use apply rather than call in try-catch integration (#4695)
fix(ember): Fix merging env config (#4714)
fix(nextjs): Add env var to suppress API non-response meta-warning (#4706)
fix(nextjs): Widen scope for client file upload (#4705)
fix(node): Fix async stack parsing (#4721)
ref(browser): Use ratelimit utils in base transport (#4686)
ref(build): Introduce root build directory in @sentry/browser (#4688)
ref(minimal): Simplify syntheticException creation (#4691)
ref(tracing): Remove BrowserTracing logging flag default value (#4708)
ref(utils): Simplify isDebugBuild logging guard (#4696)

Work in this release contributed by @Turbo87. Thank you for your contribution!

nodemailer/nodemailer

`v6.7.4`

Compare Source

Ensure compatibility with Node 18
Replaced Travis with Github Actions

`v6.7.3`

Compare Source

Typo fixes
Added stale issue automation fir Github
Add Infomaniak config to well known service (popod)
Update Outlook/Hotmail host in well known services (popod)
fix: DSN recipient gets ignored (KornKalle)

prettier/prettier

`v2.6.2`

Compare Source

diff

Fix LESS/SCSS format error (#12536 by @fisker)

// Input
.background-gradient(@&#8203;cut) {
    background: linear-gradient(
        to right,
        @&#8203;white 0%,
        @&#8203;white (@&#8203;cut - 0.01%),
        @&#8203;portal-background @&#8203;cut,
        @&#8203;portal-background 100%
    );
}

// Prettier 2.6.1
TypeError: Cannot read properties of undefined (reading 'endOffset')

// Prettier 2.6.2
.background-gradient(@&#8203;cut) {
  background: linear-gradient(
    to right,
    @&#8203;white 0%,
    @&#8203;white (@&#8203;cut - 0.01%),
    @&#8203;portal-background @&#8203;cut,
    @&#8203;portal-background 100%
  );
}

Update `meriyah` to fix several bugs (#12567 by @fisker, fixes in `meriyah` by @3cp)

Fixes bugs when parsing following valid code:

foo(await bar());

const regex = /.*/ms;

const element = <p>{/w/.test(s)}</p>;

class A extends B {
  #privateMethod() {
    super.method();
  }
}

`v2.6.1`

Compare Source

diff

Ignore `loglevel` when printing information (#12477 by @fisker)

`v2.6.0`

Compare Source

prettier --loglevel silent --find-config-path index.js

TryGhost/node-sqlite3

Thank you to everyone reporting issues with building sqlite3 or the prebuilt binaries 🙂 If you encounter an problem, please search open and closed issues for existing reports or open a new issue with as much system information as possible.

Full Changelog: TryGhost/node-sqlite3@v5.0.4...v5.0.5

`v5.0.4`

Compare Source

What's Changed

Added prebuilt Linux musl binaries - @daniellockyer
Added prebuilt Linux ARM64 binaries - @daniellockyer
Fixed older glibc compatibility - @daniellockyer

Full Changelog: TryGhost/node-sqlite3@v5.0.3...v5.0.4

visionmedia/supertest

`v6.2.3`

Compare Source

chore: bump deps 6329e2d
Merge pull request #759 from francescobarbera/master e6d371c
docs: add an example for complex object in multipart upload 729e818

TypeStrong/ts-loader

`v9.3.0`

Compare Source

simplify configuration for fork-ts-checker-webpack-plugin - thanks @piotr-oles

`v9.2.9`

Compare Source

make v9 latest following v8 release - thanks @johnnyreilly

`v9.2.8`

Compare Source

Bug fix: support webpack 5 in ts-loader [#1438] - thanks @einatbar

gilamran/tsc-watch

`v4.6.2`

Compare Source

Added file_emitted signal support when --listEmittedFiles is used issue
Added client new event file_emitted with the emitted file path

`v4.6.1`

Compare Source

Added --maxNodeMem param to set manually node allocated memory issue - (Thanks to @pp0rtal for the idea and the PR!)

dividab/tsconfig-paths

`v3.14.1`

Compare Source

Fixed

Use minimist 1.2.6 for all depencencies becuase of pollution vulnerability. See PR #197. Thanks to @gopijaganthan for this fix!

`v3.14.0`

Compare Source

Added

Support for path mapping starting with /. See PR #180, issue #113, and issue #128. Thanks to @benevbright for this fix!

typeorm/typeorm

`v0.3.6`

Compare Source

Features

add for_key_share ("FOR KEY SHARE") lock mode for postgres driver (#8879) (4687be8), closes #8878
new driver: Cloud Spanner (#8730) (62518ae)

`v0.3.5`

Compare Source

Bug Fixes

.save repository method not returning generated uuids for aurora-postgres (#8825) (ed06f4c)
allow hstore type to use transformers in driver postgres (#8823) (b1a0107)
broken shebang parameters of cli-ts-node-commonjs and cli-ts-node-esm on some linux distros (#8821) (c5dfc11), closes #8818
find select object api should support false values #8796 (#8807) (9ac8e9e)
resolve missing ConnectionOptions export in index.ts (#8850) (1693a17), closes #8837
save correct discriminator with STI (#8819) (9d1e246), closes #2927
Update DeepPartial for usage of generics with Repository class (#8817) (8ba742e)
fixed issue with typeorm init command (#8820)

`v0.3.4`

Compare Source

Bug Fixes

BaseEntity.reload method regression and made findOne to throw error on missing conditions in runtime (#8801) (ee8c1ec)
improve DeepPartial recursion (#8732) (0494008), closes #8681
missing timestamp in created migrations filenames (#8802) (ceee439)
PoolConnection leaked by MysqlDriver (#8803) (d2cfd22)
remove console.log calls from SelectQueryBuilder (#8795) (54c7db4), closes #8792
stop crashing when redis is offline and ignoreErrors on cache options is set (#8725) (edc39d1)

Features

add support for insert with alias (#4003) (#8791) (4b37030)
applicationName parameter for CockroachDB (#8800) (79b7f5c)

`v0.3.3`

Compare Source

Bug Fixes

improve initialization of custom repository (#8782) (52a641c)
resolve entities correctly in datasource when globs are specified (#8778) (a641c5d)

Features

support for Common Table Expressions (#8534) (7cc1848), closes #1116 #5899 #4753

`v0.3.2`

Compare Source

Bug Fixes

broken CLI in ESM projects since version 0.3.0 (#8773) (97699e8)

Features

add typeorm CLI variations that include ts-node (#8776) (05fc744)
allows user to specify which mysql package should be used (#8771) (35106df)

Reverts

json/jsonb change introduced in 0.3.1 (#8777) (edf27d9)

`v0.3.1`

Compare Source

Bug Fixes

bugfixes introduced in 0.3.0 (#8764) (d61f857), closes #8762 #8759 #8758 #8757

Features

new array find operators (ArrayContains, ArrayContainedBy, ArrayOverlap) (#8766) (9f1b8e3):

BREAKING CHANGES

we do not call JSON.stringify() to json/jsonb column types in Postgres. Instead, we delegate value directly to underlying pg driver. This is a correct way of handling jsons.
array: true must be explicitly defined for array json/jsonb values
strings being JSON-stringified must be manually escaped

`v0.3.0`

Compare Source

Changes in the version includes changes from the next branch and typeorm@next version.
They were pending their migration from 2018. Finally, they are in the master branch and master version.

Features

compilation target now is es2020. This requires Node.JS version 14+
TypeORM now properly works when installed within different node_modules contexts
(often happen if TypeORM is a dependency of another library or TypeORM is heavily used in monorepo projects)
Connection was renamed to DataSource.
Old Connection is still there, but now it's deprecated. It will be completely removed in next version.
New API:

export const dataSource = new DataSource({
    // ... options ...
})

// load entities, establish db connection, sync schema, etc.
await dataSource.connect()

Previously, you could use new Connection(), createConnection(), getConnectionManager().create(), etc.
They all deprecated in favour of new syntax you can see above.

New way gives you more flexibility and simplicity in usage.

new custom repositories syntax:

export const UserRepository = myDataSource.getRepository(UserEntity).extend({
    findUsersWithPhotos() {
        return this.find({
            relations: {
                photos: true
            }
        })
    }
})

Old ways of custom repository creation were dropped.

added new option on relation load strategy called relationLoadStrategy.
Relation load strategy is used on entity load and determines how relations must be loaded when you query entities and their relations from the database.
Used on find* methods and QueryBuilder. Value can be set to join or query.
- join - loads relations using SQL JOIN expression
- query - executes separate SQL queries for each relation

Default is join, but default can be set in ConnectionOptions:

createConnection({
    /* ... */
    relationLoadStrategy: "query"
})

Also, it can be set per-query in find* methods:

userRepository.find({
    relations: {
        photos: true
    }
})

And QueryBuilder:

userRepository
    .createQueryBuilder()
    .setRelationLoadStrategy("query")

For queries returning big amount of data, we recommend to use query strategy,
because it can be a more performant approach to query relations.

added new findOneBy, findOneByOrFail, findBy, countBy, findAndCountBy methods to BaseEntity, EntityManager and Repository:

const users = await userRepository.findBy({
    name: "Michael"
})

Overall find* and count* method signatures where changed, read the "breaking changes" section for more info.

new select type signature in FindOptions (used in find* methods):

userRepository.find({
    select: {
        id: true,
        firstName: true,
        lastName: true,
    }
})

Also, now it's possible to specify select columns of the loaded relations:

userRepository.find({
    select: {
        id: true,
        firstName: true,
        lastName: true,
        photo: {
            id: true,
            filename: true,
            album: {
                id: true,
                name: true,
            }
        }
    }
})

new relations type signature in FindOptions (used in find* methods):

userRepository.find({
    relations: {
        contacts: true,
        photos: true,
    }
})

To load nested relations use a following signature:

userRepository.find({
    relations: {
        contacts: true,
        photos: {
            album: true,
        },
    }
})

new order type signature in FindOptions (used in find* methods):

userRepository.find({
    order: {
        id: "ASC"
    }
})

Now supports nested order by-s:

userRepository.find({
    order: {
        photos: {
            album: {
                name: "ASC"
            },
        },
    }
})

new where type signature in FindOptions (used in find* methods) now allows to build nested statements with conditional relations, for example:

userRepository.find({
    where: {
        photos: {
            album: {
                name: "profile"
            }
        }
    }
})

Gives you users who have photos in their "profile" album.

FindOperator-s can be applied for relations in where statement, for example:

userRepository.find({
    where: {
        photos: MoreThan(10),
    }
})

Gives you users with more than 10 photos.

boolean can be applied for relations in where statement, for example:

userRepository.find({
    where: {
        photos: true
    }
})

BREAKING CHANGES

minimal Node.JS version requirement now is 14+
drop ormconfig support. ormconfig still works if you use deprecated methods,
however we do not recommend using it anymore, because it's support will be completely dropped in 0.4.0.
If you want to have your connection options defined in a separate file, you can still do it like this:

import ormconfig from "./ormconfig.json"

const MyDataSource = new DataSource(require("./ormconfig.json"))

Or even more type-safe approach with resolveJsonModule in tsconfig.json enabled:

import ormconfig from "./ormconfig.json"

const MyDataSource = new DataSource(ormconfig)

But we do not recommend use this practice, because from 0.4.0 you'll only be able to specify entities / subscribers / migrations using direct references to entity classes / schemas (see "deprecations" section).

We won't be supporting all ormconfig extensions (e.g. json, js, ts, yaml, xml, env).

support for previously deprecated migrations:* commands was removed. Use migration:* commands instead.
all commands were re-worked. Please refer to new CLI documentation.
cli option from BaseConnectionOptions (now BaseDataSourceOptions options) was removed (since CLI commands were re-worked).
now migrations are running before schema synchronization if you have both pending migrations and schema synchronization pending
(it works if you have both migrationsRun and synchronize enabled in connection options).
aurora-data-api driver now is called aurora-mysql
aurora-data-api-pg driver now is called aurora-postgres
EntityManager.connection is now EntityManager.dataSource
Repository now has a constructor (breaks classes extending Repository with custom constructor)
@TransactionRepository, @TransactionManager, @Transaction decorators were completely removed. These decorators do the things out of the TypeORM scope.
Only junction table names shortened.

MOTIVATION: We must shorten only table names generated by TypeORM.
It's user responsibility to name tables short if their RDBMS limit table name length
since it won't make sense to have table names as random hashes.
It's really better if user specify custom table name into @Entity decorator.
Also, for junction table it's possible to set a custom name using @JoinTable decorator.

findOne() signature without parameters was dropped.
If you need a single row from the db you can use a following syntax:

const [user] = await userRepository.find()

This change was made to prevent user confusion.
See this issue for details.

findOne(id) signature was dropped. Use following syntax instead:

const user = await userRepository.findOneBy({
    id: id // where id is your column name
})

This change was made to provide a more type-safe approach for data querying.
Due to this change you might need to refactor the way you load entities using MongoDB driver.

findOne, findOneOrFail, find, count, findAndCount methods now only accept FindOptions as parameter, e.g.:

const users = await userRepository.find({
    where: { /* conditions */ },
    relations: { /* relations */ }
})

To supply where conditions directly without FindOptions new methods were added:
findOneBy, findOneByOrFail, findBy, countBy, findAndCountBy. Example:

const users = await userRepository.findBy({
    name: "Michael"
})

This change was required to simply current find* and count* methods typings,
improve type safety and prevent user confusion.

findByIds was deprecated, use findBy method instead in conjunction with In operator, for example:

userRepository.findBy({
    id: In([1, 2, 3])
})

This change was made to provide a more type-safe approach for data querying.

findOne and QueryBuilder.getOne() now return null instead of undefined in the case if it didn't find anything in the database.
Logically it makes more sense to return null.
findOne now limits returning rows to 1 at database level.

NOTE: FOR UPDATE locking does not work with findOne in Oracle since FOR UPDATE cannot be used with FETCH NEXT in a single query.

where in FindOptions (e.g. find({ where: { ... })) is more sensitive to input criteria now.
FindConditions (where in FindOptions) was renamed to FindOptionsWhere.
null as value in where used in find* methods is not supported anymore.
Now you must explicitly use IsNull() operator.

Before:

userRepository.find({
    where: {
        photo: null
    }
})

After:

userRepository.find({
    where: {
        photo: IsNull()
    }
})

This change was made to make it more transparent on how to add "IS NULL" statement to final SQL,
because before it bring too much confusion for ORM users.

if you had entity properties of a non-primitive type (except Buffer) defined as columns,
then you won't be able to use it in find*'s where. Example:

Before for the @Column(/*...*/) membership: MembershipKind you could have a query like:

userRepository.find({
    membership: new MembershipKind("premium")
})

now, you need to wrap this value into Equal operator:

userRepository.find({
    membership: Equal(new MembershipKind("premium"))
})

This change is due to type-safety improvement new where signature brings.

order in FindOptions (used in find* methods) doesn't support ordering by relations anymore.
Define relation columns, and order by them instead.
where in FindOptions (used in find* methods) previously supported ObjectLiteral and string types.
Now both signatures were removed. ObjectLiteral was removed because it seriously breaks the type safety,
and string doesn't make sense in the context of FindOptions. Use QueryBuilder instead.
MongoRepository and MongoEntityManager now use new types called MongoFindManyOptions and MongoFindOneOptions
for their find* methods.
primary relation (e.g. @ManyToOne(() => User, { primary: true }) user: User) support is removed.
You still have an ability to use foreign keys as your primary keys,
however now you must explicitly define a column marked as primary.

Example, before:

@&#8203;ManyToOne(() => User, { primary: true })
user: User

Now:

@&#8203;PrimaryColumn()
userId: number

@&#8203;ManyToOne(() => User)
user: User

Primary column name must match the relation name + join column name on related entity.
If related entity has multiple primary keys, and you want to point to multiple primary keys,
you can define multiple primary columns the same way:

@&#8203;PrimaryColumn()
userFirstName: string

@&#8203;PrimaryColumn()
userLastName: string

@&#8203;ManyToOne(() => User)
user: User

This change was required to simplify ORM internals and introduce new features.

prefix relation id columns contained in embedded entities (#7432)
find by Date object in sqlite driver (#7538)
issue with non-reliable new Date(ISOString) parsing (#7796)

DEPRECATIONS

all CLI commands do not support ormconfig anymore. You must specify a file with data source instance instead.
entities, migrations, subscribers options inside DataSourceOptions accepting string directories support is deprecated.
You'll be only able to pass entity references in the future versions.
all container-related features (UseContainerOptions, ContainedType, ContainerInterface, defaultContainer,
useContainer, getFromContainer) are deprecated.
EntityManager's getCustomRepository used within transactions is deprecated. Use withRepository method instead.
Connection.isConnected is deprecated. Use .isInitialized instead.
select in FindOptions (used in find* methods) used as an array of property names is deprecated.
Now you should use a new object-literal notation. Example:

Deprecated way of loading entity relations:

userRepository.find({
    select: ["id", "firstName", "lastName"]
})

New way of loading entity relations:

userRepository.find({
    select: {
        id: true,
        firstName: true,
        lastName: true,
    }
})

This change is due to type-safety improvement new select signature brings.

relations in FindOptions (used in find* methods) used as an array of relation names is deprecated.
Now you should use a new object-literal notation. Example:

Deprecated way of loading entity relations:

userRepository.find({
    relations: ["contacts", "photos", "photos.album"]
})

New way of loading entity relations:

userRepository.find({
    relations: {
        contacts: true,
        photos: {
            album: true
        }
    }
})

This change is due to type-safety improvement new relations signature brings.

join in FindOptions (used in find* methods) is deprecated. Use QueryBuilder to build queries containing manual joins.
Connection, ConnectionOptions are deprecated, new names to use are: DataSource and DataSourceOptions.
To create the same connection you had before use a new syntax: new DataSource({ /*...*/ }).
createConnection(), createConnections() are deprecated, since Connection is called DataSource now, to create a connection and connect to the database
simply do:

const myDataSource = new DataSource({ /*...*/ })
await myDataSource.connect()

getConnection() is deprecated. To have a globally accessible connection, simply export your data source and use it in places you need it:

export const myDataSource = new DataSource({ /*...*/ })
// now you can use myDataSource anywhere in your application

getManager(), getMongoManager(), getSqljsManager(), getRepository(), getTreeRepository(), getMongoRepository(), createQueryBuilder()
are all deprecated now. Use globally accessible data source instead:

export const myDataSource = new DataSource({ /*...*/ })
export const Manager = myDataSource.manager
export const UserRepository = myDataSource.getRepository(UserEntity)
export const PhotoRepository = myDataSource.getRepository(PhotoEntity)
// ...

getConnectionManager() and ConnectionManager itself are deprecated - now Connection is called DataSource,
and each data source can be defined in exported variable. If you want to have a collection
of data sources, just define them in a variable, simply as:

const dataSource1 = new DataSource({ /*...*/ })
const dataSource2 = new DataSource({ /*...*/ })
const dataSource3 = new DataSource({ /*...*/ })

export const MyDataSources = {
    dataSource1,
    dataSource2,
    dataSource3,
}

getConnectionOptions() is deprecated - in next version we are going to implement different mechanism of connection options loading
AbstractRepository is deprecated. Use new way of custom repositories creation.
Connection.name and BaseConnectionOptions.name are deprecated. Connections don't need names anymore since we are going to drop all related methods relying on this property.
all deprecated signatures will be removed in 0.4.0

EXPERIMENTAL FEATURES NOT PORTED FROM NEXT BRANCH

observers - we will consider returning them back with new API in future versions
alternative find operators - using $any, $in, $like and other operators in where condition.

Microsoft/TypeScript

`v4.6.4`

Compare Source

This release includes a bug fix for text formatting on certain ranges, which was impacting Visual Studio users.

For the complete list of fixed issues, check out the

Downloads are available on:

`v4.6.3`

Compare Source

This release includes fixes for

For the complete list of fixed issues, check out the

Downloads are available on:

npm

Configuration

📅 Schedule: "before 3am on Monday" (UTC).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Never, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

If you want to rebase/retry this PR, click this checkbox.

This PR has been generated by WhiteSource Renovate. View repository job log here.

renovate bot force-pushed the renovate/all-packages branch from e3e3d3c to e6c497d Compare April 30, 2022 15:51

Update all-packages

4b0607f

renovate bot force-pushed the renovate/all-packages branch from e6c497d to 4b0607f Compare April 30, 2022 16:12

damienbeaufils merged commit b0669ee into master May 2, 2022

damienbeaufils deleted the renovate/all-packages branch May 2, 2022 18:34

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Update all-packages #141

Update all-packages #141

renovate bot commented Apr 4, 2022 •

edited

Update all-packages #141

Update all-packages #141

Conversation

renovate bot commented Apr 4, 2022 • edited

Release Notes

Fix LESS/SCSS format error (#​12536 by @​fisker)

Update meriyah to fix several bugs (#​12567 by @​fisker, fixes in meriyah by @​3cp)

Ignore loglevel when printing information (#​12477 by @​fisker)

What's Changed

What's Changed

What's Changed

Fixed

Added

Features

Bug Fixes

Bug Fixes

Features

Bug Fixes

Features

Bug Fixes

Features

Reverts

Bug Fixes

Features

BREAKING CHANGES

Features

BREAKING CHANGES

DEPRECATIONS

EXPERIMENTAL FEATURES NOT PORTED FROM NEXT BRANCH

Configuration

renovate bot commented Apr 4, 2022 •

edited

Fix LESS/SCSS format error (#12536 by @fisker)

Update `meriyah` to fix several bugs (#12567 by @fisker, fixes in `meriyah` by @3cp)

Ignore `loglevel` when printing information (#12477 by @fisker)