next/dist/esm/lib/framework/boundary-components.js

The React Framework

'use client';
import { METADATA_BOUNDARY_NAME, VIEWPORT_BOUNDARY_NAME, OUTLET_BOUNDARY_NAME, ROOT_LAYOUT_BOUNDARY_NAME } from './boundary-constants';
// We use a namespace object to allow us to recover the name of the function
// at runtime even when production bundling/minification is used.
const NameSpace = {
    [METADATA_BOUNDARY_NAME]: function({ children }) {
        return children;
    },
    [VIEWPORT_BOUNDARY_NAME]: function({ children }) {
        return children;
    },
    [OUTLET_BOUNDARY_NAME]: function({ children }) {
        return children;
    },
    [ROOT_LAYOUT_BOUNDARY_NAME]: function({ children }) {
        return children;
    }
};
export const MetadataBoundary = // We use slice(0) to trick the bundler into not inlining/minifying the function
// so it retains the name inferred from the namespace object
NameSpace[METADATA_BOUNDARY_NAME.slice(0)];
export const ViewportBoundary = // We use slice(0) to trick the bundler into not inlining/minifying the function
// so it retains the name inferred from the namespace object
NameSpace[VIEWPORT_BOUNDARY_NAME.slice(0)];
export const OutletBoundary = // We use slice(0) to trick the bundler into not inlining/minifying the function
// so it retains the name inferred from the namespace object
NameSpace[OUTLET_BOUNDARY_NAME.slice(0)];
export const RootLayoutBoundary = // We use slice(0) to trick the bundler into not inlining/minifying the function
// so it retains the name inferred from the namespace object
NameSpace[ROOT_LAYOUT_BOUNDARY_NAME.slice(0)];

//# sourceMappingURL=boundary-components.js.map