Important: This documentation covers Yarn 1 (Classic).
For Yarn 2+ docs and migration guide, see yarnpkg.com.

Package detail

@scalar/build-tooling

scalar466MIT0.1.12TypeScript support: included

Build tooling and helpers

readme

Scalar Build Tooling

This package provides essential build and development tools for managing packages within the scalar/scalar repository. It includes:

  • Standardized build scripts for Rollup and Vite
  • Type checking and building utilities
  • Code formatting and linting tools
  • Configurations for various build scenarios

These tools streamline the development process, ensure consistency across packages, and optimize the build output for different project types within the monorepo.

Usage

By default, all dependencies are externalized, and we don’t bundle anything for internal modules.

For deployed web applications, alternative build methods should be used to provide a complete client bundle. This ensures that all necessary dependencies are included for the end-user.

To use these build tools effectively, all package.json files should include the following scripts:

"scripts": {
  "build": "scalar-build-rollup",
  "types:check": "scalar-types-check",
  "types:build": "scalar-types-build",
  "format": "scalar-format-js",
  "lint:check": "eslint .",
  "lint:fix": "eslint . --fix",
}

For Vite/Vue we need a different build command that uses Vite and vue-tsc:

"scripts": {
  "build": "scalar-build-vite",
  "types:check": "scalar-types-check-vue",
  "types:build": "scalar-types-build-vue",
  "format": "scalar-format-js",
  "lint:check": "eslint .",
  "lint:fix": "eslint . --fix",
}

Rollup

For non-Vue projects, we use Rollup for builds due to its superior tree-shaking capabilities. This approach optimizes our bundle size.

Our Rollup configuration provides out-of-the-box support for importing JSON, YAML, and CSS files. Additionally, you can easily copy static files by specifying entries in the copy parameter.

Here’s an example of a basic rollup.config.ts file:

import type { RollupOptions } from 'rollup'

import { createRollupConfig } from './src/rollup-options'

const options: RollupOptions = {
  // Specify the entry point(s) for your build
  input: ['./src/index.ts'],
  // Alternative: Use findEntryPoints for multiple entry points with TypeScript and CSS support
  // input: await findEntryPoints({ allowCss: true }),
  ...createRollupConfig({
    // Enable TypeScript support
    typescript: true,

    // Additional options can be added here to customize the build
  }),
}

// Export the Rollup configuration
export default options

Vite

For Vue projects, we use Vite to build production code. Vite offers superior performance and a more streamlined development experience compared to traditional build tools.

While Vite uses Rollup under the hood for production builds, it provides additional optimizations and features specifically tailored for Vue projects. Most Rollup options can still be passed through, allowing for fine-grained control over the build process.

A basic Vite configuration for a Vue project might look like this:

import {
  alias,
  createViteBuildOptions,
  findEntryPoints,
} from '@scalar/build-tooling'
import vue from '@vitejs/plugin-vue'
import { defineConfig } from 'vitest/config'

export default defineConfig({
  plugins: [vue()],
  resolve: {
    // Provides @ -> './src' and @test -> './test' aliases
    alias: alias(),
  },
  server: {
    port: 5000,
  },
  build: createViteBuildOptions({
    entry: await findEntryPoints({ allowCss: true }),
  }),
})

changelog

@scalar/build-tooling

0.1.12

Patch Changes

  • a40999d: chore: added type safety rule noUncheckedIndexedAccess

0.1.11

Patch Changes

  • e911047: Add default exports

0.1.10

Patch Changes

  • 2a1b5f4: Prevent dist deletion in vite builds

0.1.9

Patch Changes

  • 7cb664a: feat: rollup removes dist folder by default

0.1.8

Patch Changes

  • 397faa4: Add property for workspace path to vite reload watcher

0.1.7

Patch Changes

  • 94e68ab: chore: upgrade typescript to 5.5

0.1.6

Patch Changes

  • e0fc110: chore: patch bump all package

0.1.5

Patch Changes

  • 689677a: fix: auto importing css backup
  • 8494349: Migrate to highlightjs based syntax highlighting
  • b38c7ed: Update build configs to a standardized format
  • 6fbb57e: feat: release all the packages

0.1.4

Patch Changes

  • 45dc04b: fix: can’t release packages

0.1.3

Patch Changes

  • 05e2e27: chore: add provenance statement

0.1.2

Patch Changes

  • 22f2858: chore: ran syncpack to update packages

0.1.1

Patch Changes

  • 2488ddd: Add trailing space for package file saving

0.1.0

Minor Changes

  • 7fb8273: Migrate to @scalar/openapi-parser

0.0.4

Patch Changes

  • cecf074: Migrate to oas utils for basic spec operations

0.0.3

Patch Changes

  • 313997c: chore: align node versions to basis 18

0.0.2

Patch Changes

  • c254604: Add OAS utils package