vike/dist/utils/assertRoutingType.js

The Framework *You* Control - Next.js & Nuxt alternative for unprecedented flexibility and dependability.

export { assertClientRouting };
export { assertServerRouting };
export { checkIfClientRouting };
import { assertUsage, assertWarning } from './assert.js';
import { getGlobalObject } from './getGlobalObject.js';
import { isBrowser } from './isBrowser.js';
import pc from '@brillout/picocolors';
const state = getGlobalObject('utils/assertRouterType.ts', {});
function assertClientRouting() {
    assertNoContradiction(checkIfClientRouting());
    state.isClientRouting = true;
}
function checkIfClientRouting() {
    return state.isClientRouting !== false;
}
function assertServerRouting() {
    assertNoContradiction(state.isClientRouting !== true);
    state.isClientRouting = false;
}
function assertNoContradiction(noContradiction) {
    // If an assertion fails because of a wrong usage, then we assume that the user is trying to import from 'vike/client/router' while not setting `clientRouting` to `true`. Note that 'vike/client' only exports the type `PageContextBuiltInClient` and that the package.json#exports entry 'vike/client' will eventually be removed.
    assertUsage(isBrowser(), `${pc.cyan("import { something } from 'vike/client/router'")} is forbidden on the server-side`, { showStackTrace: true });
    assertWarning(noContradiction, "You shouldn't `import { something } from 'vike/client/router'` when using Server Routing. The 'vike/client/router' utilities work only with Client Routing. In particular, don't `import { navigate }` nor `import { prefetch }` as they unnecessarily bloat your client-side bundle sizes.", { showStackTrace: true, onlyOnce: true });
}