st-start

library2.0.0-beta.48jsnpmunverified

An opinionated, zero-configuration TypeScript project bundler & starter for frontend and Node.js, version 2.0.0-beta.48. It wraps webpack and babel with stable plugins to provide fast builds, multi-threaded type checking, HMR, and code splitting. Supports modern CSS (PostCSS, LostGrid, SASS), CSS modules with types, ESM, and auto-polyfilling via Browserslist. Includes ESLint linting, .env support, gzip compression, and an HTML artifact graph analyzer. Differentiates from other bundlers by promising a minimal or no config file, focusing on TypeScript-first workflows, and emphasizing robustness and developer experience with clear error messages and desktop notifications. Released under the MIT license and maintained by the SpringType organization, it is part of a larger ecosystem but remains a standalone tool.

devops web-framework testing

npm install st-start

package ↗homepage ↗

INSTALL

IMPORT

SIG · ST-START

st-start

devopsjavascriptv2.0.0-beta.48

Install

—

Import

—

Disk

—

Pass rate

0/ 6

Env Coverage0 / 6

glibc

18–22

musl

18–22

Install & Compatibility

Where this runs

tested against v? · npm install

Install × environment matrix

Each cell = how many times install + import succeeded across repeated harness runs. Partial = flaky.
glibc = Debian/Ubuntu slim · musl = Alpine Linux

musl

node 18–226 runs

build_error

glibc

node 18–226 runs

build_error

Code

Verified usage

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

st-start (CLI)

✓ npx st-start

✗ import st-start from 'st-start'

st-start is a CLI tool; it should be invoked via `npx st-start` or as a script in package.json. Do not try to import it directly in code.

BuildConfig

✓ import { BuildConfig } from 'st-start'

✗ const BuildConfig = require('st-start').BuildConfig

Since version 2, st-start is ESM-first. Use named imports from the package if you need config types.

st.config.js

✓ module.exports = { /* config */ }

✗ export default { /* config */ }

The configuration file must be a CommonJS module (module.exports). ESM is not supported for st.config.js.

Sets up a new project with st-start: installs the bundler, creates package.json scripts, and shows minimal entry files (HTML and TSX) to get a dev server running.

// 1. Install st-start as a dev dependency npm install -D st-start // 2. Add scripts to package.json { "scripts": { "start": "st-start", "build": "st-start -env production" } } // 3. Create src/index.html as entry HTML // <!DOCTYPE html> // <html> // <head><title>My App</title></head> // <body><div id="root"></div></body> // </html> // 4. Create src/index.tsx as entry TypeScript // import React from 'react'; // import ReactDOM from 'react-dom'; // ReactDOM.render(<h1>Hello World</h1>, document.getElementById('root')); // 5. Run the start script npm run start

st-start --version

Debug

Known issues

breakingst-start v2 is a complete rewrite over v1. Configuration options and CLI flags may have changed.

fix

Refer to the v2 documentation and update your st.config.js accordingly. Run `st-start -h` to see current CLI options.

affects: >=2.0.0

deprecatedESM syntax in st.config.js is not supported; only CommonJS module.exports works.

fix

Use `module.exports = { ... }` instead of `export default { ... }`.

affects: >=2.0.0

gotchast-start does not support direct import/require of its internals. The package is a CLI tool; use it via command line, not as a library.

fix

Use `npx st-start` or run via npm scripts. Do not `import st-start` in your code.

affects: *

gotchaThe bundler uses webpack under the hood; advanced webpack customizations might conflict with st-start's presets.

fix

Avoid custom webpack configs; rely on st-start's configuration options (st.config.js). If you need deep customization, consider using webpack directly.

affects: *

Errors

Common errors & fixes

Cannot find module 'st-start'

st-start is not installed or not in node_modules, or you tried to import it in code instead of running CLI.

fix

Ensure `npm install -D st-start` is run. Use `npx st-start` to execute CLI, not a require/import.

You may need an appropriate loader to handle this file type

st-start does not include a loader for certain file types (e.g., .vue, .svelte).

fix

st-start only supports TypeScript, JavaScript, CSS, SASS, and images. For other file types, you may need to extend the webpack config manually.

TypeScript: Cannot use import statement outside a module

Your tsconfig.json may not have 'module' set to 'ESNext' or 'CommonJS', or the file is not treated as a module.

fix

Ensure `tsconfig.json` has `"module": "ESNext"` for st-start's dynamic imports to work, or adjust your project structure.

Upgrade

Version history

2.0.0-beta.48latest on npm

Audit

Dependencies

webpackrequiredCore bundler used under the hood; st-start wraps webpack with pre-configured options.

babelrequiredTranspilation of TypeScript and JavaScript; relies on babel for backwards compatibility.

typescriptrequiredTypeScript compilation and type checking are core to the bundler; must be installed.

Agent activity

6 hits · last 30 days

node

Resources

packagehttps://www.npmjs.com/package/st-start ↗

homepagehttps://springtype.dev/st-start ↗