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

import React from 'react'
import { DocumentProps } from './utils'

export const DocumentContext = React.createContext<DocumentProps>(null as any)

if (process.env.NODE_ENV !== 'production') {
  DocumentContext.displayName = 'DocumentContext'
}
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 _document context (#9068) 2019-10-14 18:45:56 +02:00			`import { DocumentProps } from './utils'`

Support persisting the dev cache buster (#15827) Same as #15483 but couldn't push to it --- Closes #15483 Fixes #15828 2020-08-03 16:22:55 +02:00			`export const DocumentContext = React.createContext<DocumentProps>(null as any)`
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') {`
			`DocumentContext.displayName = 'DocumentContext'`
			`}`