remove notes on workaround

emily-shen · emily-shen · commit 531890060ec7 · 2025-07-28T13:05:48.000+01:00
diff --git a/src/content/docs/workers/runtime-apis/rpc/typescript.mdx b/src/content/docs/workers/runtime-apis/rpc/typescript.mdx
@@ -28,10 +28,6 @@ For example, if your client Worker had bindings to a Worker in `../sum-worker/`
 	}
 />
 
-:::note
-Currently, this only works if your service binding targets a [named entrypoint](/workers/runtime-apis/bindings/service-bindings/rpc/#named-entrypoints), rather than the default export. If you are unable to use named entrypoints, we recommend you extend your `Env` type in a separate file in order to manually provide those types without risk of being overwritten by subsequent runs of `wrangler types`. This is a temporary limitation we are working to fix.
-:::
-
 This will produce a `worker-configuration.d.ts` file that includes:
 
 ```ts title="worker-configuration.d.ts"
diff --git a/src/content/docs/workers/wrangler/commands.mdx b/src/content/docs/workers/wrangler/commands.mdx
@@ -1989,9 +1989,6 @@ wrangler types [<PATH>] [OPTIONS]
   	SERVICE_BINDING: Service<import("../bound-worker/src/index").Entrypoint>;
   }
   ```
-  :::note
-  Currently, this only works if your service binding targets a [named entrypoint](/workers/runtime-apis/bindings/service-bindings/rpc/#named-entrypoints), rather than the default export. If you are unable to use named entrypoints, we recommend you extend your `Env` type in a separate file in order to manually provide those types without risk of being overwritten by subsequent runs of `wrangler types`. This is a temporary limitation we are working to fix.
-  :::
 
 ---
 

Original file line number	Diff line number	Diff line change
@@ -28,10 +28,6 @@ For example, if your client Worker had bindings to a Worker in `../sum-worker/`
`28`	`28`	`}`
`29`	`29`	`/>`
`30`	`30`
`31`		`-:::note`
`32`		-Currently, this only works if your service binding targets a [named entrypoint](/workers/runtime-apis/bindings/service-bindings/rpc/#named-entrypoints), rather than the default export. If you are unable to use named entrypoints, we recommend you extend your `Env` type in a separate file in order to manually provide those types without risk of being overwritten by subsequent runs of `wrangler types`. This is a temporary limitation we are working to fix.
`33`		`-:::`
`34`		`-`
`35`	`31`	This will produce a `worker-configuration.d.ts` file that includes:
`36`	`32`
`37`	`33`	```ts title="worker-configuration.d.ts"
Original file line number	Diff line number	Diff line change
`@@ -1989,9 +1989,6 @@ wrangler types [<PATH>] [OPTIONS]`
`1989`	`1989`	`SERVICE_BINDING: Service<import("../bound-worker/src/index").Entrypoint>;`
`1990`	`1990`	`}`
`1991`	`1991`	```
`1992`		`- :::note`
`1993`		- Currently, this only works if your service binding targets a [named entrypoint](/workers/runtime-apis/bindings/service-bindings/rpc/#named-entrypoints), rather than the default export. If you are unable to use named entrypoints, we recommend you extend your `Env` type in a separate file in order to manually provide those types without risk of being overwritten by subsequent runs of `wrangler types`. This is a temporary limitation we are working to fix.
`1994`		`- :::`
`1995`	`1992`
`1996`	`1993`	`---`
`1997`	`1994`