chore: update package locks

[dhmlau]

Ran npm run update-package-locks to update the package lock files.

cc @samarpanB

Checklist

• DCO (Developer Certificate of Origin) signed in all commits
• npm test passes on your machine
• New tests added or existing tests modified to cover all changes
• Code conforms with the style guide
• API Documentation in code was updated
• Documentation in /docs/site was updated
• Affected artifact templates in packages/cli were updated
• Affected example projects in examples/* were updated

👉 Check out how to submit a PR 👈

[samarpanB]

Some tests failing. Not sure if those are due to this change or not.

[frbuceta]

I have not seen this PR. I have merge a commit that fixes the update problem but it gives a problem in the Sequelize extension.

[frbuceta]

It's failing here

loopback-next/extensions/sequelize/src/sequelize/sequelize.repository.base.ts

Line 274 in c9c35c9

const data = await this.sequelizeModel.findByPk(

It is a method of Sequelize. See https://sequelize.org/docs/v6/core-concepts/model-querying-finders/#findbypk

[frbuceta]

I have found the problem. Sequelize creates a column of type array in INTEGER. That is what is giving problems.

loopback-next/extensions/sequelize/src/sequelize/sequelize.repository.base.ts

Lines 765 to 771 in c9c35c9

	if (
	definition[propName].type === Array ||
	['Array', 'array'].includes(definition[propName].type.toString())
	) {
	// Postgres only
	dataType = DataTypes.ARRAY(DataTypes.INTEGER);
	}

[samarpan-b]

I have asked @shubhamp-sf to check it.

[shubhamp-sf]

@frbuceta It's actually the underlying package (sqlite3) upgrade in this PR that caused this issue.

I've also reported the same on their repo, please go through the issue summary here: TryGhost/node-sqlite3#1694

I had reported this to @dhmlau in this renovate PR: #9367 (comment)

cc: @samarpan-b

[shubhamp-sf]

Just raised a fix to use the working version of sqlite3 statically (until it gets fixed in the upstream) #9547

Also Diana, @frbuceta already pushed the lock maintenance 3 days back. Doesn't it already includes the changes this PR addresses?

[samarpanB]

@dhmlau after this PR - #9547, tests are now passing. I think this PR is not needed anymore.

[dhmlau]

@samarpanB @shubhamp-sf, should we close this PR then?