rsnext/packages/next/shared/lib/loadable-context.ts

'use client'

import React from 'react'

type CaptureFn = (moduleName: string) => void

export const LoadableContext = React.createContext<CaptureFn | null>(null)

if (process.env.NODE_ENV !== 'production') {
  LoadableContext.displayName = 'LoadableContext'
}
Implement loadable with lazy and suspense for next dynamic (#42589) ### Summary Migrate `next/dynamic` to implementation based on `React.lazy` and `Suspense`. Then it becomes easier to migrate the existing code in pages to layouts. Then we can support both `ssr` and `loading` option for `next/dynamic`. For `loading` option, it will work like `Suspense`'s `fallback` property ```js <Suspense fallback={loading}> <DynamicComponent /> </Suspense> ``` For `ssr` option, by default `React.lazy` supports SSR, but we'll disable the `ssr: false` case for dynamic import in server components since there's no client side involved. Then we don't need `suspense` option anymore as react >= 18 is always required. Mark it as deprecated. It also supports to load client component dynamically in server components now. #### Code code changes * switch loadable component to `lazy` + `Suspense` * will make sure it's retuning a module from `loader()` to `loader().then(mod => ({ default: mod.default \|\| mod }))` since `lazy()` only accepts loader returning a module * Inside suspense boundary, throwing an error for ssr: false, catch the error on server and client side and ignore it. * Ignore options like ssr: false for server components since they're on server, doesn't make sense * Remove legacy dynamic related transform #### Feature changes * `next/dynamic` will work in the same way across the board (appDir and pages) * For the throwing error, will make it become a API that throws error later in the future, so users can customize more with `Suspense` * You can load client components now in server components with dynamic. Resolves #43147 #### Tests * existing dynamic tests all work * add case: import client component and load through next/dynamic in server components ### Issues 2022-12-07 19:42:10 +01:00			`'use client'`

Add sourcemaps to Next.js core compilation (#13049) * Generate sourcemaps for core files that pass through Babel * Run files through Babel instead of tsc * Get rid of wildcard helper * Get rid of wildcard helper * Remove unused file * Update wildcard imports * Add exclude * Get rid of object-assign helper * Use Object.assign as it gives better output Co-authored-by: Joe Haddad <joe.haddad@zeit.co> 2020-05-19 09:09:59 +02:00			`import React from 'react'`
Remove PropTypes from _error and next/dynamic (#6763) * Remove proptypes * Remove loadable capture in favor of React.createContext * Add loadable context file * Make sure we use the context value instead 2019-03-23 21:00:31 +01:00
			`type CaptureFn = (moduleName: string) => void`

Remove ts-ignore where possible (#10541) * Remove ts-ignore where possible And replace by typecasts * More accurate types * bend cliententries in a correct shape earlier on * comment becomes unnecessary * add webpack overload to allow for the next.js use case * Avoid changing public interface Co-authored-by: Joe Haddad <timer150@gmail.com> 2020-02-17 22:16:19 +01:00			`export const LoadableContext = React.createContext<CaptureFn \| null>(null)`
Add displayName property to React Context objects (#11829) https://reactjs.org/docs/context.html#contextdisplayname Use the .displayName property to show distinct component names in React DevTools. For example, “DocumentContext.Provider” instead of just “Context.Provider”. 2020-04-13 11:55:42 +02:00
			`if (process.env.NODE_ENV !== 'production') {`
			`LoadableContext.displayName = 'LoadableContext'`
			`}`