rsnext/packages/next/server/node-polyfill-web-streams.js

import Primitives from 'next/dist/compiled/@edge-runtime/primitives'

// Polyfill Web Streams for the Node.js runtime.
if (!global.ReadableStream) {
  global.ReadableStream = Primitives.ReadableStream
}
if (!global.TransformStream) {
  global.TransformStream = Primitives.TransformStream
}
Use Edge Runtime for running Edge Functions locally (#37024) This PR introduces [Edge Runtime](https://edge-runtime.vercel.app/) for emulating [Edge Functions](https://vercel.com/features/edge-functions) locally. Every time you run a [middleware](https://nextjs.org/docs/advanced-features/middleware) locally via `next dev`, an isolated edge runtime context will be created. These contexts have the same constraints as production servers, plus they don't pollute the global scope; Instead, all the code run in a vm on top of a Node.js process. Additionally, `@edge-runtime/jest-environment` has been added to make easier testing Edge Functions in a programmatic way. It dropped the following polyfills from Next.js codebase, since they are now part of Edge Runtime: - abort-controller - formdata - uuid - web-crypto - web-streams Co-authored-by: Gal Schlezinger <2054772+Schniz@users.noreply.github.com> 2022-05-30 14:01:36 +02:00			`import Primitives from 'next/dist/compiled/@edge-runtime/primitives'`
Use `ReadableStream` in `RenderResult` (#34005) Since we're always using `ReadableStream`, we should just get rid of `ResultPiper`. This also lets us replace things like `bufferedReadFromReadableStream` with a `TransformStream` that does the same thing, so that it's `TransformStream`s all the way down. Finally, we can get rid of the one-off call to `renderToReadableStream` and just use `renderToStream` whenever we're rendering a concurrent tree. 2022-02-05 02:13:02 +01:00
Update polyfill of web streams (#35571) * attach pipeTo and pipeThrough polyfills to instance * remove transformer polyfill * remove polyfill * fix missing polyfill in sandbox * always polyfill the runtime * always polyfill web streams in renderer * fix missing AbortController and AbortSignal * type fix * fix type generation * use global Co-authored-by: Shu Ding <shu@shus-mac-studio.localdomain> 2022-04-07 16:26:30 +02:00			`// Polyfill Web Streams for the Node.js runtime.`
Use `ReadableStream` in `RenderResult` (#34005) Since we're always using `ReadableStream`, we should just get rid of `ResultPiper`. This also lets us replace things like `bufferedReadFromReadableStream` with a `TransformStream` that does the same thing, so that it's `TransformStream`s all the way down. Finally, we can get rid of the one-off call to `renderToReadableStream` and just use `renderToStream` whenever we're rendering a concurrent tree. 2022-02-05 02:13:02 +01:00			`if (!global.ReadableStream) {`
Use Edge Runtime for running Edge Functions locally (#37024) This PR introduces [Edge Runtime](https://edge-runtime.vercel.app/) for emulating [Edge Functions](https://vercel.com/features/edge-functions) locally. Every time you run a [middleware](https://nextjs.org/docs/advanced-features/middleware) locally via `next dev`, an isolated edge runtime context will be created. These contexts have the same constraints as production servers, plus they don't pollute the global scope; Instead, all the code run in a vm on top of a Node.js process. Additionally, `@edge-runtime/jest-environment` has been added to make easier testing Edge Functions in a programmatic way. It dropped the following polyfills from Next.js codebase, since they are now part of Edge Runtime: - abort-controller - formdata - uuid - web-crypto - web-streams Co-authored-by: Gal Schlezinger <2054772+Schniz@users.noreply.github.com> 2022-05-30 14:01:36 +02:00			`global.ReadableStream = Primitives.ReadableStream`
Update polyfill of web streams (#35571) * attach pipeTo and pipeThrough polyfills to instance * remove transformer polyfill * remove polyfill * fix missing polyfill in sandbox * always polyfill the runtime * always polyfill web streams in renderer * fix missing AbortController and AbortSignal * type fix * fix type generation * use global Co-authored-by: Shu Ding <shu@shus-mac-studio.localdomain> 2022-04-07 16:26:30 +02:00			`}`
			`if (!global.TransformStream) {`
Use Edge Runtime for running Edge Functions locally (#37024) This PR introduces [Edge Runtime](https://edge-runtime.vercel.app/) for emulating [Edge Functions](https://vercel.com/features/edge-functions) locally. Every time you run a [middleware](https://nextjs.org/docs/advanced-features/middleware) locally via `next dev`, an isolated edge runtime context will be created. These contexts have the same constraints as production servers, plus they don't pollute the global scope; Instead, all the code run in a vm on top of a Node.js process. Additionally, `@edge-runtime/jest-environment` has been added to make easier testing Edge Functions in a programmatic way. It dropped the following polyfills from Next.js codebase, since they are now part of Edge Runtime: - abort-controller - formdata - uuid - web-crypto - web-streams Co-authored-by: Gal Schlezinger <2054772+Schniz@users.noreply.github.com> 2022-05-30 14:01:36 +02:00			`global.TransformStream = Primitives.TransformStream`
Use `ReadableStream` in `RenderResult` (#34005) Since we're always using `ReadableStream`, we should just get rid of `ResultPiper`. This also lets us replace things like `bufferedReadFromReadableStream` with a `TransformStream` that does the same thing, so that it's `TransformStream`s all the way down. Finally, we can get rid of the one-off call to `renderToReadableStream` and just use `renderToStream` whenever we're rendering a concurrent tree. 2022-02-05 02:13:02 +01:00			`}`