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

import * as 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'
}
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			`import * as React from 'react'`

			`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'`
			`}`