Registry / devops / unplugin-atscript

unplugin-atscript

library0.1.69jsnpmunverified

Unplugin-based build tool integration for Atscript (.as) model files. Compiles .as files during development, providing TypeScript types, runtime validation, and DB metadata from a single model definition. Current stable version 0.1.69, release cadence follows Atscript monorepo. Supports Vite, Webpack, Rollup, Rolldown, esbuild, Rspack, and Farm via dedicated entry points (e.g. unplugin-atscript/vite). Requires @atscript/core and @atscript/typescript as peer dependencies. Differentiator: universal bundler support, strict validation by default, tree-shaking aware.

devops

npm install unplugin-atscript

github ↗package ↗homepage ↗

INSTALL

IMPORT

SIG · UNPLUGIN-ATSCRIPT

unplugin-atscript

devopsjavascriptv0.1.69

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.

unplugin-atscript/vite

✓ import atscript from 'unplugin-atscript/vite'

✗ import atscript from 'unplugin-atscript'

Must use specific entry point for your bundler; default import is incorrect.

unplugin-atscript/rollup

✓ import atscript from 'unplugin-atscript/rollup'

✗ const atscript = require('unplugin-atscript/rollup')

ESM-only; CommonJS require not supported.

unplugin-atscript/webpack

✓ const atscript = require('unplugin-atscript/webpack')

✗ import atscript from 'unplugin-atscript/webpack'

webpack entry point supports CommonJS require; ESM import may not work depending on webpack version.

atscript()

✓ atscript()

✗ new atscript()

The plugin is a factory function, not a class. Do not use 'new'.

Shows how to integrate unplugin-atscript with Vite using proper entry point and plugin initialization.

// vite.config.ts import atscript from 'unplugin-atscript/vite' import { defineConfig } from 'vite' export default defineConfig({ plugins: [ atscript({ // optional: set strict: false to allow .as errors without failing build // strict: true is default }) ] })

Debug

Known issues

breakingPassing plugin options incorrectly may cause build failures

fix

Always call atscript() as a function, not with 'new'. Options object is optional.

affects: >=0.1.0

gotchaWrong import path — must use bundler-specific subpath

fix

Use 'unplugin-atscript/vite', 'unplugin-atscript/webpack', etc. Do not import from 'unplugin-atscript'.

affects: >=0.1.0

gotchaPeer dependencies not installed will cause runtime errors

fix

Ensure @atscript/core and @atscript/typescript are in devDependencies.

affects: >=0.1.0

deprecatedFarm support is experimental and entry point may change

fix

Monitor documentation for updates; use 'unplugin-atscript/farm' with caution.

affects: >=0.1.0

Errors

Common errors & fixes

Cannot find module 'unplugin-atscript'

Importing from general package name instead of subpath

fix

Change import to specific bundler subpath, e.g. 'unplugin-atscript/vite'.

TypeError: atscript is not a constructor

Using 'new atscript()' instead of calling atscript()

fix

Remove 'new' keyword: use atscript() directly.

Cannot find module '@atscript/core' or '@atscript/typescript'

Missing required peer dependencies

fix

Run: pnpm add -D @atscript/core @atscript/typescript

Upgrade

Version history

0.1.69latest on npm

Audit

Dependencies

@atscript/corerequiredPeer dependency required for runtime validation and DB metadata generation

@atscript/typescriptrequiredPeer dependency required for TypeScript type generation

unpluginrequiredCore unplugin library used for bundler-agnostic plugin interface

Agent activity

4 hits · last 30 days

node

Resources

githubhttps://github.com/moostjs/atscript ↗

packageunplugin-atscript ↗

homepagehttps://github.com/moostjs/atscript/tree/main/packages/unplugin#readme ↗