feat: add turborepo for improved monorepo development experience

[abretonc7s]

Description

This PR introduces Turborepo to optimize our monorepo's development workflow, particularly focusing on the core SDK packages.

🔍 Key Changes

• Added Turborepo configuration with optimized task definitions for build, dev, lint, and type checking
• Introduced parallel development command dev:core to simultaneously work on core SDK packages
• Updated package scripts for consistent watch/dev modes across packages
• Added concurrently for improved development experience in SDK packages

💡 Implementation Details

• Configured turbo.json with:
  • Task dependencies and caching rules
  • Global env variable handling
  • Persistent dev mode for better DX
• Added dev scripts in core packages to support concurrent typescript compilation and rollup bundling
• Standardized build outputs and cache management

[socket-security]

New dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/[email protected]	environment, filesystem, shell	+1	413 kB	gustavohenke
npm/[email protected]	None	0	30 MB	turbobot
npm/[email protected]	None	0	26.2 MB	turbobot
npm/[email protected]	None	0	32.6 MB	turbobot
npm/[email protected]	None	0	27.6 MB	turbobot
npm/[email protected]	None	0	40.2 MB	turbobot
npm/[email protected]	None	0	40.2 MB	turbobot
npm/[email protected]	None	0	14.9 kB	turbobot
npm/[email protected]	None	0	138 B	jaredpalmer

View full report↗︎

[socket-security]

👍 Dependency issues cleared. Learn more about Socket for GitHub ↗︎

This PR previously contained dependency changes with security issues that have been resolved, removed, or ignored.

Ignoring: npm/[email protected]

View full report↗︎

Next steps

Take a deeper look at the dependency

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 [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/[email protected] or ignore all packages with @SocketSecurity ignore-all

[abretonc7s]

@SocketSecurity ignore npm/[email protected]

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 74.02%. Comparing base (1e40815) to head (e943b9c).
Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1195   +/-   ##
=======================================
  Coverage   74.02%   74.02%           
=======================================
  Files         182      182           
  Lines        4343     4343           
  Branches     1064     1064           
=======================================
  Hits         3215     3215           
  Misses       1128     1128           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud