diff --git a/src/frontend/src/content/docs/deployment/javascript-apps.mdx b/src/frontend/src/content/docs/deployment/javascript-apps.mdx index cb81f93ead..b31bec6b68 100644 --- a/src/frontend/src/content/docs/deployment/javascript-apps.mdx +++ b/src/frontend/src/content/docs/deployment/javascript-apps.mdx @@ -35,10 +35,6 @@ To deploy a JavaScript app, choose which resource owns the public HTTP surface i - Use a JavaScript publish method when the JavaScript app resource should become the deployed static website or Node.js server. - Use `AddNextJsApp(...)` for a Next.js app that publishes as a standalone Next.js server. -:::caution[Experimental] -The JavaScript app resource publish methods and `AddNextJsApp` are marked `[Experimental]` and require suppressing the `ASPIREJAVASCRIPT001` diagnostic. -::: - If you only add a Vite or JavaScript app and reference backend services, Aspire still needs one of these production hosting patterns to know who serves requests in deployment. During publish or deploy, Aspire validates that build-only containers are either consumed by another resource through `PublishWithContainerFiles(...)` or `PublishWithStaticFiles(...)`, or converted into a deployable JavaScript resource with a JavaScript publish method. An unconsumed build-only container does not participate in deployment.