chore: Switch to turborepo

[janjakubnanista]

In this PR

• Switch from cd xxx && npm i to a turbo based setup that mirrors sdk (in fact, it has been largely if not completely copied from there). This brings a lot of goodies in
• Add TypeScript support (only affecting test files though)
• Fix some JSDOC comments to make TypeScript happy
• Fix JSDOM test setup so that we can remove the triplicated verifyEnclaveSignature function from tests. Basically the tests were testing that a mocked function works as expected

[socket-security]

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

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	jest-environment-jsdom@​30.4.1
	jest@​30.4.2
	@​typescript-eslint/​parser@​8.63.0
	@​types/​jsdom@​28.0.3
	stream-browserify@​3.0.0
	@​types/​jest@​30.0.0
	@​typescript-eslint/​eslint-plugin@​8.63.0
	ts-node@​10.9.2
	rollup-plugin-node-externals@​6.1.2
	crypto-browserify@​3.12.1
	util@​0.12.5
	@​rollup/​plugin-typescript@​11.1.6
	turbo@​2.10.4
	typescript@​5.9.3 ⏵ 5.4.3	+1		+1	-4
	ts-jest@​29.4.11
	ts-loader@​9.6.2
	rollup@​4.59.0

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 "▶" to expand/collapse)
Warn		Obfuscated code: npm data-urls is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: pnpm-lock.yaml → npm/jest-environment-jsdom@30.4.1 → npm/data-urls@5.0.0 ℹ Read more on: This package | This alert | What is obfuscated code? 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 support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/data-urls@5.0.0. 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.
Warn		Obfuscated code: npm node-forge is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: pnpm-lock.yaml → npm/webpack-dev-server@5.2.2 → npm/node-forge@1.4.0 ℹ Read more on: This package | This alert | What is obfuscated code? 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 support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/node-forge@1.4.0. 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.
Warn		Obfuscated code: npm rrweb-cssom is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: pnpm-lock.yaml → npm/jest-environment-jsdom@30.4.1 → npm/rrweb-cssom@0.8.0 ℹ Read more on: This package | This alert | What is obfuscated code? 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 support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/rrweb-cssom@0.8.0. 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.
Warn		Obfuscated code: npm yargs is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: pnpm-lock.yaml → npm/jest@30.4.2 → npm/jest@29.7.0 → npm/yargs@17.7.3 ℹ Read more on: This package | This alert | What is obfuscated code? 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 support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/yargs@17.7.3. 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

[justinformentin]

We currently have doc outlining a plan to do just this - convert to a monorepo and typescript.

We are going to approach this as a multi-step change to make it possible to review and confirm everything still works and behaves the exact same way. This is too large of a change for a single PR.

[janjakubnanista]

@justinformentin same thoughts - although turbo is just one of many pieces of the puzzle.

#125 contains everything needed to get this repo up to speed:

• turbo
• Removing that nasty string replacement in k8s resources in favour of nginx SSI
• Optimized Dockerfile
• Dev setup
• E2E tests coming

The PR is massive and the idea is to split it up into 10+ I guess steps. But to make it safe, E2E regression test suite is essential. To make things difficult, of course is much harder to add it first, then introduce turbo, but it's doable.

Also for browser testing (vitest using playwright), a runtime code change is required. The test runtime runs as an iframe, we then create yet another iframe and our iframe now triggers an error in isDoublyIframed.