move ManagedRuntime.TypeId to fix circular imports

[leonitousconforti]

Type

• Refactor
• Feature
• Bug Fix
• Optimization
• Documentation Update

Description

Right now, there is two typeId definitions for effect/ManagedRuntime, one in layer and one in managedRuntime. If you change one of them then everything still type-checks, but it would not be correct. Would this be an appropriate solution? Didn't make a public MemoMap file because I didn't think it warranted changing the public Layer file

Related

• Related Issue #
• Closes #

[changeset-bot]

🦋 Changeset detected

Latest commit: 145169c

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 32 packages

Name	Type
effect	Patch
@effect/cli	Patch
@effect/cluster-browser	Patch
@effect/cluster-node	Patch
@effect/cluster-workflow	Patch
@effect/cluster	Patch
@effect/experimental	Patch
@effect/opentelemetry	Patch
@effect/platform-browser	Patch
@effect/platform-bun	Patch
@effect/platform-node-shared	Patch
@effect/platform-node	Patch
@effect/platform	Patch
@effect/printer-ansi	Patch
@effect/printer	Patch
@effect/rpc-http	Patch
@effect/rpc	Patch
@effect/schema	Patch
@effect/sql-d1	Patch
@effect/sql-drizzle	Patch
@effect/sql-kysely	Patch
@effect/sql-libsql	Patch
@effect/sql-mssql	Patch
@effect/sql-mysql2	Patch
@effect/sql-pg	Patch
@effect/sql-sqlite-bun	Patch
@effect/sql-sqlite-node	Patch
@effect/sql-sqlite-react-native	Patch
@effect/sql-sqlite-wasm	Patch
@effect/sql	Patch
@effect/typeclass	Patch
@effect/vitest	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[mikearnaldi]

/rebase

[tim-smart]

I think in this case we could just move the ManagedRuntime.TypeId to a internal/managedRuntime/circular.ts file.

We can keep memo map in the layer module.