@jpcw/configs

Shared TypeScript / ESLint / Prettier configs and a small CLI for JPCW projects.

In honor and memory of Forrest Jones. C# > TS.

Three presets:

• suitescript — NetSuite SuiteScript 2.x (TS targeting AMD/ES2021, CRLF, modern typescript-eslint). Lints Node.js built-in imports as errors (they don't exist in the NS runtime) and requires the @NApiVersion / @NScriptType governance JSDoc on files under SuiteScripts/. Ships a separate tsconfig.spa.json for React SPAs bundled into a Suitelet.
• react — React for the web (Vite + ES2022 + JSX, LF, jsx-a11y)
• react-native — React Native / Expo (no DOM lib, __DEV__ global, jsx: react-native)

Modern flat-config ESLint (no airbnb / no FlatCompat), projectService: true for fast type-aware lint, Prettier owns formatting.

Install in a new project

init scaffolds everything: .gitignore, .editorconfig, tsconfig.json, eslint.config.mjs, prettier.config.mjs, .vscode/settings.json, and a starter package.json with deps already wired up. It's idempotent — re-running on an existing project only adds what's missing.

SuiteScript

mkdir my-suitescript-project && cd my-suitescript-project
git init
npx -p @jpcw/configs jpcw-configs init suitescript --pm yarn   # or --pm npm | --pm bun
yarn install

Replace the PROJECT_NAME and REPLACE_WITH_SDF_AUTH_ID_* placeholders in package.json, then yarn install.

The scaffolded tsconfig.json extends @jpcw/configs/suitescript/tsconfig.json. Want full strict mode? Switch the extends to @jpcw/configs/suitescript/tsconfig.strict.json.

React (web)

mkdir my-react-project && cd my-react-project
git init
npx -p @jpcw/configs jpcw-configs init react --pm bun   # or yarn | npm
bun install                                             # match your --pm

React Native (Expo)

mkdir my-rn-project && cd my-rn-project
git init
npx -p @jpcw/configs jpcw-configs init react-native --pm yarn
yarn install

The RN preset assumes Expo + Expo Router. If you're on bare RN, drop expo-router from package.json and adjust main.

What gets written

| File | Purpose | |---|---| | .gitignore | Per-preset ignores (Node, build artifacts, IDE, secrets, plus SDF for suitescript / native + Expo for react-native) | | .prettierignore | Per-preset Prettier ignores (build output, lockfiles; native dirs for react-native) | | tsconfig.spa.json | suitescript only — bundler/react-jsx tsconfig for a React SPA served by a Suitelet (source under src/spa/) | | .editorconfig | Tabs/EOL source of truth (CRLF for suitescript, LF for react/react-native) | | .vscode/settings.json | Format-on-save, ESLint flat-config mode, Prettier as default formatter | | tsconfig.json | Extends the preset; project-specific paths/include filled in | | eslint.config.mjs | One-line re-export of the preset | | prettier.config.mjs | One-line re-export of the preset | | package.json | Pinned deps, lint/lint:fix/format/format:write/typecheck scripts, SDF auth scripts (suitescript) | | .yarnrc.yml | Yarn-only, with nodeLinker: node-modules (required for SDF tooling on suitescript) |

Migrate an existing project

If you currently extend @interiorworx/netsuite-customization-configs (or have raw inlined configs):

1. Install the package alongside what's there. It won't conflict.

   yarn add -D @jpcw/configs

2. Run init. It only adds missing scripts/devDependencies and skips files that already exist (--force overrides .gitignore).

   npx @jpcw/configs init suitescript

   init adds deps at the template's pinned versions. If you're migrating an old repo and want the toolchain at current versions (instead of bumping eslint/typescript/etc. by hand, as you may have been doing), follow with upgrade — or scaffold with init suitescript --latest to do both at once:

   npx @jpcw/configs upgrade suitescript            # toolchain → current
   npx @jpcw/configs upgrade suitescript --dry-run  # preview first

3. If you had tsconfig.json / eslint.config.mjs / prettier.config.mjs, init skipped them. Either delete yours and re-run, or swap the extends / re-export by hand:

   - "extends": "./node_modules/@interiorworx/netsuite-customization-configs/configs/tsconfig.json",
   + "extends": "@jpcw/configs/suitescript/tsconfig.json",

4. Replace any old .eslintrc.json with the scaffolded eslint.config.mjs (ESLint 9 flat config) and delete the old file.

5. Replace any old .prettierrc with the scaffolded prettier.config.mjs and delete the old file.

6. Replace writeProjectJSON.js calls in package.json scripts with the CLI:

   - "MWC-SB":   "node writeProjectJSON.js SB",
   - "MWC-PROD": "node writeProjectJSON.js PROD",
   + "MWC-SB":   "jpcw-configs write-project-json --auth 7027364_SB1-Adm-Sand",
   + "MWC-PROD": "jpcw-configs write-project-json --auth 7027364-Adm-Prod",

   Then delete writeProjectJSON.js from the repo.

7. Drop the old dep:

   yarn remove @interiorworx/netsuite-customization-configs

8. Verify:

   yarn typecheck
   yarn lint
   yarn format
   yarn run MWC-SB    # or your env script

CLI reference

jpcw-configs init <preset>

Scaffolds a project with the preset's config files. Idempotent — re-running only adds what's missing.

jpcw-configs init suitescript --pm yarn
jpcw-configs init react       --pm bun
jpcw-configs init react-native --pm yarn

| Flag | Default | Behavior | |---|---|---| | --pm <yarn\|npm\|bun> | yarn | Pins packageManager in package.json and drops in PM-specific files (e.g. .yarnrc.yml). | | --force | off | Overwrites an existing .gitignore. Other config files are skipped if they already exist (delete first to re-scaffold). | | --latest | off | After scaffolding, runs upgrade <preset> so the toolchain installs at current versions instead of the template pins. |

jpcw-configs upgrade <preset>

The template package.json ships reproducible pinned versions — good for a deterministic scaffold, but they go stale. upgrade resolves the managed dependency set to whatever is current at the moment you run it, by delegating to your package manager. Run it the day you scaffold, or a year later when you init into an old client repo — it picks up whatever is newest then, with no template re-pinning required.

jpcw-configs upgrade suitescript                     # bump the toolchain to latest
jpcw-configs upgrade react --include-frameworks      # also bump react/vite
jpcw-configs upgrade react-native --include-frameworks --dry-run

The managed set is read straight from the preset template, so it tracks the preset automatically. Deps are split:

• Toolchain (eslint, prettier, typescript, @jpcw/configs, @types/*, vite, …) — always taken at @latest. The preset is built around current tooling.
• Framework / native (react, react-dom, expo, expo-router, react-native, …) — version-sensitive, so skipped unless --include-frameworks. For the react-native preset these never go to npm-latest (that breaks the Expo SDK); they're realigned via npx expo install expo@latest && npx expo install --fix, which keeps them SDK-correct.

| Flag | Default | Behavior | |---|---|---| | --pm <yarn\|npm\|bun> | auto | Detected from packageManager / lockfile if omitted. | | --include-frameworks | off | Also upgrade framework/native deps (Expo via expo install). | | --dry-run | off | Print the package-manager commands without running them. |

jpcw-configs write-project-json --auth <id>

Writes a SuiteCloud SDK project.json (pretty-printed). Replaces the per-project writeProjectJSON.js pattern.

jpcw-configs write-project-json --auth 7027364_SB1-Adm-Sand

| Flag | Default | Meaning | |---|---|---| | --auth | required | SDF auth ID for the target NetSuite account | | --asv | ERROR | accountSpecificValues strategy (ERROR or WARNING) | | --out | project.json | output path, relative to cwd |

Maintaining this package

Branching / git hygiene

Work on main for small changes, branch for anything that touches preset behavior (rule additions/removals are user-visible). Tag every published version (npm version does this for you).

git checkout -b feat/some-change
# ...edits...
git add -A
git commit -m "feat(react): add some-change"
git push -u origin feat/some-change
gh pr create
# after merge:
git checkout main && git pull

Bumping the version

Use npm version so the git tag and package.json stay in lockstep. Pick:

• patch — bug fix, internal refactor, doc changes (no rule changes)
• minor — new preset, new rule additions, new CLI flag
• major — rule removals, rule severity bumps (warn → error), config option renames, dropping a preset, anything that could break a downstream lint or build

# from a clean main
npm version patch     # or minor / major
git push --follow-tags

npm version will:

• bump version in package.json
• create a commit (v0.2.1)
• create a matching git tag

Publishing to npm

The package is published as @jpcw/configs with public access. You need to be logged in (npm whoami to check; npm login if not).

The convenience scripts in package.json chain bump → publish → push:

yarn release:patch    # bump patch, publish, push tags
yarn release:minor
yarn release:major

If you've already bumped manually:

yarn publish:current  # = npm publish --access public

After publishing, smoke-test on a real client repo:

cd ~/git/clients/<some-project>
yarn add -D @jpcw/configs@latest
yarn install
yarn lint && yarn typecheck

Pre-publish checklist

• [ ] Updated README.md if behavior or flags changed
• [ ] Bumped template @jpcw/configs version pins (suitescript/react/react-native templates/package.json) if the version is a major bump
• [ ] Ran yarn install locally — .pnp.cjs / yarn.lock are clean
• [ ] No stray console.log / debug code in src/cli/
• [ ] Tag and tarball look right: npm pack --dry-run

What goes in the tarball

Controlled by files in package.json. As of 0.2.x:

bin/             # jpcw-configs CLI entry
src/             # CLI source
suitescript/     # preset configs + templates
react/           # preset configs + templates
react-native/    # preset configs + templates
README.md
LICENSE

.idea/, yarn.lock, .pnp.cjs and the like are excluded.

Versioning

Semver. Breaking changes to any preset are major bumps; new rules / new lints are minor.