Update lib package dependencies using yarn

[didierkrux]

npm install was not working with a fresh install but I managed to make it work using yarn instead.

[netlify]

✅ Deploy Preview for devcon-monorepo ready!

Name	Link
🔨 Latest commit	8a6fa20
🔍 Latest deploy log	https://app.netlify.com/projects/devcon-monorepo/deploys/6826fa4788d51f0008b19124
😎 Deploy Preview	https://deploy-preview-40--devcon-monorepo.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[netlify]

✅ Deploy Preview for devcon-archive-monorepo ready!

Name	Link
🔨 Latest commit	8a6fa20
🔍 Latest deploy log	https://app.netlify.com/projects/devcon-archive-monorepo/deploys/6826fa48b974c50008003d40
😎 Deploy Preview	https://deploy-preview-40--devcon-archive-monorepo.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[netlify]

❌ Deploy Preview for devconnect-monorepo failed.

Name	Link
🔨 Latest commit	8a6fa20
🔍 Latest deploy log	https://app.netlify.com/projects/devconnect-monorepo/deploys/6826fa474418c30008a9c4b8

[netlify]

✅ Deploy Preview for devcon-app ready!

Name	Link
🔨 Latest commit	8a6fa20
🔍 Latest deploy log	https://app.netlify.com/projects/devcon-app/deploys/6826fa48eb11dc0008e13ea6
😎 Deploy Preview	https://deploy-preview-40--devcon-app.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[netlify]

✅ Deploy Preview for devcon-archive ready!

Name	Link
🔨 Latest commit	8a6fa20
🔍 Latest deploy log	https://app.netlify.com/projects/devcon-archive/deploys/6826fa48384ed10008b0b4fc
😎 Deploy Preview	https://deploy-preview-40--devcon-archive.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[netlify]

✅ Deploy Preview for devcon-social ready!

Name	Link
🔨 Latest commit	8a6fa20
🔍 Latest deploy log	https://app.netlify.com/projects/devcon-social/deploys/6826fa4881b360000884fc12
😎 Deploy Preview	https://deploy-preview-40--devcon-social.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[lassejaco]

Nice, can you try to remove the package-lock.json (and confirm it works after doing so with a clean install)? Ideally we only have one lockfile to avoid confusion in the future

PS. the CI errors in github can be ignored

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	next@​13.4.9
	node-releases@​2.0.13
	typedarray@​0.0.6
	hasown@​2.0.0
	fs-constants@​1.0.0
	is-core-module@​2.13.1
	is-arrayish@​0.3.2
	strict-uri-encode@​2.0.0
	stats.js@​0.17.0
	react-merge-refs@​2.1.1
	core-util-is@​1.0.3
	chownr@​1.1.4
	tunnel-agent@​0.6.0
	glsl-token-string@​1.0.1
	process-nextick-args@​2.0.1
See 197 more rows in the dashboard

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert (click for details)
Warn		[email protected] has a Critical CVE. CVE: GHSA-f82v-jwr5-mffw Authorization Bypass in Next.js Middleware (CRITICAL) Affected versions: >= 13.0.0, < 13.5.9 Patched version: 13.5.9 From: devcon-app/package.json → npm/[email protected] ℹ Read more on: This package | This alert | What is a critical CVE? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

[didierkrux]

@lassejaco clean install seems to be working now after removing the package-lock.json file.
I also updated the README files.