Lex
npm install @nlabs/lex> Zero Configuration. Maximum Productivity.
Lex is the all-in-one development CLI that eliminates the complexity of modern React development. No more juggling webpack configs, testing setups, or build tools. Just install Lex globally and focus on what matters most - building amazing applications.






- Works out of the box with any React project
- No webpack configs to write
- No testing setup to configure
- No build tools to manage
- SWC-powered compilation (10-100x faster than Babel)
- Hot reloading development server
- Optimized production builds
- Parallel test execution
- AI-assisted error fixing
- Intelligent test generation
- Code optimization suggestions
- Smart linting with auto-fix
- TypeScript support out of the box
- Jest testing framework included
- Storybook integration
- Production-optimized builds
``bashInstall Lex globally
npm install -g @nlabs/lex
What's Included
Lex comes with everything you need for modern React development:
| Tool | Purpose | Version |
|------|---------|---------|
| SWC | Lightning-fast TypeScript/JavaScript compiler | Latest |
| Jest | Testing framework | Latest |
| TypeScript | Type safety | Latest |
| Webpack | Advanced bundling | Latest |
| Storybook | Component development | Latest |
| PostCSS | CSS processing | Latest |
| ESLint | Code linting | Latest |
Commands Overview
$3
| Command | Description | Quick Example |
|---------|-------------|---------------|
|
lex init | Create new React applications | lex init my-app --typescript |
| lex create | Generate project assets | lex create view Dashboard |
| lex migrate | Migrate existing projects | lex migrate |$3
| Command | Description | Quick Example |
|---------|-------------|---------------|
|
lex dev | Start development server | lex dev --open |
| lex serverless | Start serverless development server | lex serverless --host 0.0.0.0 |
| lex compile | Compile TypeScript/JavaScript | lex compile --watch |
| lex build | Build for production | lex build --mode production |$3
| Command | Description | Quick Example |
|---------|-------------|---------------|
|
lex test | Run Jest tests | lex test --watch |
| lex lint | Lint code with ESLint | lex lint --fix |
| lex storybook | Start Storybook | lex storybook --open |$3
| Command | Description | Quick Example |
|---------|-------------|---------------|
|
lex ai | AI code assistance | lex ai --task generate --prompt "Create a button component" |
| lex test | AI test generation | lex test --generate |
| lex build | AI error fixing | lex build --assist |$3
| Command | Description | Quick Example |
|---------|-------------|---------------|
|
lex update | Update dependencies | lex update --interactive |
| lex upgrade | Upgrade Lex itself | lex upgrade |
| lex publish | Publish to npm | lex publish --bump minor |$3
| Command | Description | Quick Example |
|---------|-------------|---------------|
|
lex clean | Clean project files | lex clean |
| lex copy | Copy files/directories | lex copy src lib |
| lex config | Show configurations | lex config webpack |
| lex versions | Show tool versions | lex versions |
| lex link | Check linked modules | lex link |Core Features
$3
`bash
Start with hot reloading
lex dev --openWith bundle analyzer
lex dev --bundleAnalyzerCustom webpack config
lex dev --config ./custom.webpack.jsForce refresh cached public IP
lex dev --usePublicIp
`Public IP Caching: Lex automatically caches your public IP address for 1 week to reduce API calls. Use
--usePublicIp to force refresh the cache when needed.Static Assets: If your HTML template references static assets (like favicon.ico, manifest.json, or images) with absolute paths, ensure these files exist in your source directory or use relative paths to avoid webpack compilation errors.
Static Assets: Use the
webpack.staticPath configuration to specify a directory for static assets (images, videos, audio, PDFs, etc.). Files in this directory will be automatically copied to the output and optimized for web delivery.$3
`bash
Start serverless development server
lex serverlessWith custom host and ports
lex serverless --host 0.0.0.0 --httpPort 4000 --wsPort 4002With environment variables
lex serverless --variables '{"NODE_ENV":"development","API_KEY":"test"}'With GraphQL debug logging
lex serverless --debug --printOutput
`AWS Lambda Simulation: Lex provides a local development server similar to serverless-offline, allowing you to test AWS Lambda functions with HTTP and WebSocket support.
Configuration: Configure your serverless functions in
lex.config.mjs. See the Serverless Documentation for detailed configuration options.Environment Variables: The serverless command automatically loads environment variables from
.env, .env.local, and .env.development files, with command-line variables taking precedence.$3
`bash
Standard production build
lex build --mode productionWith SWC (faster)
lex build --bundler swcWith AI optimization analysis
lex build --analyze
`$3
`bash
Run all tests
lex testWatch mode
lex test --watchGenerate tests with AI
lex test --generateDebug failing tests
lex test --debugTestsUse project-specific Jest config
lex test --config ./jest.config.js
`#### Advanced Testing Features
- Smart Configuration Merging: Automatically merges your project's Jest config with Lex's optimized defaults
- ESM Support: Automatic detection and configuration for ES modules projects
- Automatic Setup: Creates jest.setup.js file if one doesn't exist
- React JSX Automatic Runtime: No need to import React in your test files
- TypeScript-First: Optimized for TypeScript projects with specialized configs
$3
`bash
Start Storybook
lex storybook --openWith Tailwind CSS support
lex storybook --useLexConfigBuild static site
lex storybook --static
`$3
`bash
Generate code
lex ai --task generate --prompt "Create a user profile component"Explain code
lex ai --task explain --file src/components/Button.tsxFix errors
lex ai --task help --prompt "Fix this TypeScript error"
`Framework Support
Lex works seamlessly with popular React frameworks and libraries:
- ✅ Create React App - Migrate existing CRA projects
- ✅ Next.js - Use Lex for testing and building
- ✅ Gatsby - Integrate Lex workflows
- ✅ Vite - Alternative to Vite for complex projects
- ✅ TypeScript - Full TypeScript support out of the box
- ✅ Tailwind CSS - Automatic Tailwind integration
- ✅ Storybook - Built-in Storybook support
- ✅ Serverless - Local AWS Lambda development with HTTP/WebSocket support
🚀 Performance
Lex is designed for speed and efficiency:
- SWC Integration - 10-100x faster than Babel, faster than esbuild
- Smart Caching - Intelligent caching for faster rebuilds
- Hot Reloading - Instant feedback during development
- Tree Shaking - Automatic dead code elimination
- Code Splitting - Automatic code splitting for optimal loading
Configuration
Lex works out of the box, but you can customize it with a
lex.config.js file:`javascript
export default {
// Project settings
useTypescript: true,
sourcePath: './src',
outputPath: './lib', // Package manager
packageManager: 'npm',
// AI configuration
ai: {
provider: 'openai',
model: 'gpt-4'
},
// SWC configuration (defaults to ESM format)
// SWC is now the default transpiler for all compilation tasks
// Jest configuration (merged with Lex defaults)
jest: {
testEnvironment: 'jsdom',
setupFilesAfterEnv: ['./src/setupTests.js'],
moduleNameMapper: {
'\\.(css|less|scss|sass)$': 'identity-obj-proxy'
}
}
};
`Configuration Options Reference
Lex provides extensive configuration options through the
lex.config.js file. Here's a comprehensive reference of all available options:$3
| Option | Type | Default | Description | Example |
|--------|------|---------|-------------|---------|
|
entryHTML | string | 'index.html' | HTML template file | entryHTML: 'app.html' |
| entryJs | string | 'index.js' | Main JavaScript entry file | entryJs: 'main.tsx' |
| outputFile | string | undefined | Specific output filename | outputFile: 'bundle.js' |
| outputFullPath | string | path.resolve('./lib') | Absolute output path for build artifacts. Used by webpack dev server for static file serving. | outputFullPath: '/absolute/build' |
| outputHash | boolean | false | Add hash to output filenames | outputHash: true |
| outputPath | string | './lib' | Output directory path | outputPath: './build' |
| packageManager | 'npm' \| 'yarn' | 'npm' | Package manager to use | packageManager: 'yarn' |
| preset | 'web' \| 'node' \| 'lambda' \| 'mobile' | 'web' | Project preset type | preset: 'node' |
| sourceFullPath | string | path.resolve('./src') | Absolute source code path | sourceFullPath: '/absolute/path' |
| sourcePath | string | './src' | Source code directory path | sourcePath: './app' |
| targetEnvironment | 'web' \| 'node' | 'web' | Target runtime environment | targetEnvironment: 'node' |
| useGraphQl | boolean | false | Enable GraphQL support | useGraphQl: true |
| useTypescript | boolean | false | Enable TypeScript support | useTypescript: true |$3
| Option | Type | Default | Description | Example |
|--------|------|---------|-------------|---------|
|
ai.apiKey | string | undefined | API key for AI provider | ai: { apiKey: 'sk-...' } |
| ai.maxTokens | number | 4000 | Maximum tokens for AI responses | ai: { maxTokens: 8000 } |
| ai.model | string | 'gpt-4o' | AI model to use | ai: { model: 'gpt-4' } |
| ai.provider | 'cursor' \| 'copilot' \| 'openai' \| 'anthropic' \| 'none' | 'none' | AI service provider | ai: { provider: 'openai' } |
| ai.temperature | number | 0.1 | AI response creativity (0-1) | ai: { temperature: 0.7 } |$3
SWC (Speedy Web Compiler) is now the default transpiler for all TypeScript and JavaScript compilation in Lex. SWC provides:
- 10-100x faster compilation than Babel
- Faster than esbuild for TypeScript compilation
- Zero configuration - works out of the box
- ESM by default - modern module format
- Automatic React JSX transformation
- TypeScript decorators support
SWC is automatically configured and doesn't require additional configuration in most cases. The default settings provide optimal performance and compatibility.
| Feature | Description | Default |
|---------|-------------|---------|
| Output Format | JavaScript module format |
esm |
| Target | JavaScript target version | es2020 |
| JSX Runtime | React JSX transformation | automatic |
| Decorators | TypeScript decorators support | enabled |
| Source Maps | Debug information | inline |$3
| Option | Type | Default | Description | Example |
|--------|------|---------|-------------|---------|
|
jest.extensionsToTreatAsEsm | string[] | undefined | Extensions to treat as ES modules | jest: { extensionsToTreatAsEsm: ['.ts', '.tsx'] } |
| jest.moduleNameMapper | Record | undefined | Module name mappings | jest: { moduleNameMapper: { '\\.(css)$': 'identity-obj-proxy' } } |
| jest.preset | string | undefined | Jest preset | jest: { preset: 'ts-jest' } |
| jest.roots | string[] | undefined | Test root directories | jest: { roots: [' |
| jest.testEnvironment | string | undefined | Test environment | jest: { testEnvironment: 'jsdom' } |
| jest.transform | Record | undefined | Transform configurations | jest: { transform: { '^.+\\.tsx?$': ['ts-jest'] } } |
| jest.transformIgnorePatterns | string[] | undefined | Patterns to ignore in transforms | jest: { transformIgnorePatterns: ['node_modules'] } |$3
Lex provides a default ESLint configuration optimized for React and TypeScript projects. To extend Lex's ESLint config, create an
eslint.config.mjs file in your project root that imports and spreads Lex's configuration.How it works:
- Lex uses ESLint's flat config format (array-based configuration)
- Create an
eslint.config.mjs file that imports @nlabs/lex/eslint.config.mjs and spreads it
- Add your custom rules as additional objects in the array
- If you don't create an eslint.config.mjs, Lex will use its default configuration automaticallyRecommended approach - Create
eslint.config.mjs:`javascript
// eslint.config.mjs
import lexConfig from '@nlabs/lex/eslint.config.mjs';export default [
...lexConfig,
{
rules: {
'no-console': 'warn',
'@typescript-eslint/no-unused-vars': 'error'
}
}
];
`Alternative - Use
lex.config.* (limited):You can also specify ESLint rules in your
lex.config.js file, but this is less flexible:| Option | Type | Default | Description | Example |
|--------|------|---------|-------------|---------|
|
eslint.extends | string[] | undefined | Additional ESLint configs to extend | eslint: { extends: ['@typescript-eslint/recommended'] } |
| eslint.rules | Linter.RulesRecord | undefined | Custom ESLint rules | eslint: { rules: { 'no-console': 'warn' } } |Note: Creating an
eslint.config.mjs file gives you full control and is the recommended approach. The lex.config.* approach is provided for simple rule overrides only.$3
| Option | Type | Default | Description | Example |
|--------|------|---------|-------------|---------|
|
webpack.entry | string \| string[] | undefined | Webpack entry points | webpack: { entry: './src/index.js' } |
| webpack.module | object | undefined | Webpack module configuration | webpack: { module: { rules: [...] } } |
| webpack.output | object | undefined | Webpack output configuration | webpack: { output: { filename: 'bundle.js' } } |
| webpack.plugins | unknown[] | undefined | Webpack plugins | webpack: { plugins: [new MyPlugin()] } |
| webpack.staticPath | string | './src/static' | Path to static assets directory. Files in this directory will be copied to the output and optimized (images/videos compressed, audio optimized) | webpack: { staticPath: './assets' } |$3
| Option | Type | Default | Description | Example |
|--------|------|---------|-------------|---------|
|
libraryName | string | undefined | Library name for UMD builds | libraryName: 'MyLibrary' |
| libraryTarget | string | undefined | Library target format | libraryTarget: 'umd' |$3
| Option | Type | Default | Description | Example |
|--------|------|---------|-------------|---------|
|
configFiles | string[] | [] | Additional config files to include | configFiles: ['./config/custom.js'] |
| copyFiles | string[] | [] | Files to copy during build | copyFiles: ['public/assets'] |
| env | object | null | Environment variables | env: { NODE_ENV: 'development' } |
| gitUrl | string | undefined | Git repository URL | gitUrl: 'https://github.com/user/repo' |$3
#### Basic TypeScript Project
`javascript
export default {
useTypescript: true,
sourcePath: './src',
outputPath: './lib',
preset: 'web',
targetEnvironment: 'web'
};
`#### Node.js Library
`javascript
export default {
useTypescript: true,
preset: 'node',
targetEnvironment: 'node',
libraryName: 'MyLibrary',
libraryTarget: 'umd'
// SWC automatically handles Node.js compilation with optimal settings
};
`#### AI-Powered Development
`javascript
export default {
useTypescript: true,
ai: {
provider: 'openai',
apiKey: process.env.OPENAI_API_KEY,
model: 'gpt-4',
maxTokens: 8000,
temperature: 0.3
},
jest: {
testEnvironment: 'jsdom',
setupFilesAfterEnv: ['./src/setupTests.ts']
}
};
`#### Advanced SWC Configuration
`javascript
export default {
useTypescript: true
// SWC provides optimal defaults for all compilation tasks
// No additional configuration needed for most use cases
// SWC automatically handles:
// - ESM output format (default)
// - ES2020 target
// - React JSX transformation
// - TypeScript decorators
// - Source map generation
};
`#### Custom ESLint Configuration
Option 1: Create
eslint.config.mjs (Recommended)`javascript
// eslint.config.mjs
import lexConfig from '@nlabs/lex/eslint.config.mjs';export default [
...lexConfig,
{
rules: {
'no-console': 'warn',
'@typescript-eslint/explicit-function-return-type': 'off',
'react/prop-types': 'off' // Not needed with TypeScript
}
}
];
`Option 2: Use
lex.config.* (Simple overrides only)`javascript
// lex.config.js
export default {
useTypescript: true,
eslint: {
rules: {
'no-console': 'warn',
'@typescript-eslint/explicit-function-return-type': 'off'
}
}
};
`Troubleshooting
$3
#### 404 Error with "Static Paths" Message
If you see a 404 error with a message like "Static Paths /path/to/lib", this is likely because the webpack dev server is trying to serve static files from a directory that doesn't exist yet.
Solution: The
outputFullPath directory should exist before starting the dev server. You can:- Run
lex build first to create the output directory
- Or ensure your outputPath configuration points to an existing directory#### Port Already in Use
If you get an "address already in use" error, another process is using the default port (3000).
Solution: Kill the existing process or use a different port:
`bash
Kill processes on port 3000
lsof -ti:3000 | xargs kill -9Or use a different port
lex dev --port 3000
`#### TypeScript Configuration Issues
If TypeScript compilation fails, ensure your
tsconfig.json is properly configured.Solution: Check that your
tsconfig.json includes the correct paths:`json
{
"compilerOptions": {
"outDir": "./lib",
"rootDir": "./src"
},
"include": ["src/*/"],
"exclude": ["node_modules", "lib"]
}
`#### Missing Static Assets Error
If you see webpack compilation errors about missing static assets (like favicon.ico, manifest.json, or images), this is because your HTML template references files that don't exist.
Solution: Either create the missing files or update your HTML template to use relative paths:
`html
`Or create the missing files in your source directory:
`bash
touch src/favicon.ico
touch src/manifest.json
mkdir -p src/images && touch src/images/logo-icon-64.png
`Documentation
- 📖 Full Documentation - Complete API reference
- 🎯 Getting Started Guide - Step-by-step tutorial
- 🛠️ Configuration Guide - Customization options
- 🤖 AI Features Guide - AI-powered development
- 🧪 Testing Guide - Testing best practices
Contributing
We love contributions! Here's how you can help:
1. Fork the repository
2. Create a feature branch (
git checkout -b feature/amazing-feature)
3. Commit your changes (git commit -m 'Add amazing feature')
4. Push to the branch (git push origin feature/amazing-feature)
5. Open a Pull Request$3
`bash
Clone the repository
git clone https://github.com/nitrogenlabs/lex.gitInstall dependencies
npm installRun tests
npm testBuild the project
npm run build
``This project is licensed under the MIT License - see the LICENSE file for details.
- SWC - For lightning-fast TypeScript/JavaScript compilation
- Jest - For comprehensive testing
- TypeScript - For type safety
- Webpack - For advanced bundling features
- Storybook - For component development
- OpenAI/Anthropic - For AI-powered features
- Issues - GitHub Issues
- Discussions - GitHub Discussions
- Email -
- Twitter - @NitrogenLabs
---
Made with ❤️ by Nitrogen Labs
Lex - Because development should be effortless.