Registry / devops / sapper-limited-minifier

sapper-limited-minifier

JSON →
library0.28.10jsnpmunverified

Sapper is a framework for building high-performance universal (SSR) web applications with Svelte, similar to Next.js. It provides file-based routing, server-side rendering, code splitting, and offline support via service workers. The current stable version is 0.28.10, but development has shifted to SvelteKit (the successor). Sapper uses Rollup or Webpack for bundling and requires Svelte ^3.17.3 as a peer dependency. It is now in maintenance mode; new projects should use SvelteKit instead.

npm install sapper-limited-minifier
INSTALL
IMPORT
SIG · SAPPER-LIMITED-MIN
S
sapper-limited-minifier
devopsjavascriptv0.28.10
harness data pending
Install & Compatibility
Where this runs

No compatibility data collected yet for this library.

Code
Verified usage

Verified import paths — ran on the pinned version, not inferred.

default (start function)
import sapper from '@sapper/server';
const sapper = require('@sapper/server');
Sapper is ESM-only; CommonJS require may fail or produce undefined.
middleware
import { middleware } from '@sapper/server';
const { middleware } = require('@sapper/server');
Direct import of middleware function for Express/Polka integrations.
stores (session, page, preloading)
import { stores } from '@sapper/app';
import { stores } from 'sapper';
Client-side stores are exported from '@sapper/app', not the main package.

Shows minimal Express server setup with Sapper middleware for SSR and client-side routing.

// server.js (Express) import express from 'express'; import sapper from '@sapper/server'; import { middleware } from '@sapper/server'; const app = express(); app.use(sapper()); app.listen(process.env.PORT || 3000);
Debug
Known issues
deprecatedSapper is deprecated in favor of SvelteKit. New projects should use SvelteKit.
fix
Migrate to SvelteKit (https://kit.svelte.dev) for continued support and new features.
affects: >=0.28.0
gotchaSapper's middleware import differs between client and server code.
fix
Use '@sapper/app' for client-side code and '@sapper/server' for server-side code.
affects: *
breakingSapper 0.28 dropped support for Rollup config export pattern.
fix
If using a custom Rollup config, ensure it exports an array, not a function returning an array.
affects: >=0.28.0
gotchaService worker must be a separate entry point named 'service-worker.js' in the src directory.
fix
Place service worker at src/service-worker.js; do not import inside Svelte components.
affects: *
gotchaSapper does not support dynamic imports inside Svelte components for code splitting; it splits pages automatically.
fix
Use Sapper's built-in code splitting via file-based routing, not manual dynamic imports in components.
affects: *
Errors
Common errors & fixes
Cannot find module '@sapper/server'
Misconfigured path or missing dependency.
fix
Ensure '@sapper/server' is installed: npm install @sapper/server. For SvelteKit projects, use 'svelte' package instead.
export { default as sapper } from '@sapper/server'; // not working
Sapper does not export default from the server package after version 0.28.
fix
Use named exports: import { middleware } from '@sapper/server'; or import sapper from '@sapper/server'; (default export)
Uncaught SyntaxError: Unexpected token 'export'
Trying to use ESM in a CommonJS only context (e.g., Node.js without --experimental-modules or type: module).
fix
Set 'type': 'module' in package.json or use Node >=14 with --experimental-modules.
Cannot read property 'page' of undefined (stores context)
Trying to access stores (e.g., stores().page) outside of a Svelte component that is rendered by Sapper.
fix
Only call stores() inside a Svelte component that is part of a Sapper page (e.g., .svelte files in routes/).
Upgrade
Version history
0.28.10latest on npm
Audit
Dependencies
svelterequiredPeer dependency; Sapper requires Svelte ^3.17.3 to compile components.
Agent activity
5 hits · last 30 days
node
4
Resources
sapper-limited-minifier — npm install sapper-limited-minifier · libregistry