@mnaoumov/create-obsidian-plugin 1.0.2 → 1.1.0

package/templates/default/dprint.json_framework.ejs

@@ -0,0 +1,10 @@
+{
+  "extends": "./node_modules/@mnaoumov/obsidian-dev-toolkit/dist/templates/dprint.json",
+  "excludes": [
+    "dist",
+    "**/node_modules",
+    "**/*-lock.json",
+    "**/*.md",
+    "demo-vault"<%- render('excludes') %>
+  ]
+}

package/templates/default/dprint.json_framework@excludes_docs-showcase.ejs

@@ -0,0 +1,2 @@
+,
+    "src/docs"

package/templates/default/dprint.json_standalone.ejs

@@ -6,6 +6,7 @@
     "exportDeclaration.forceMultiLine": "whenMultiple",
     "functionExpression.spaceAfterFunctionKeyword": true,
     "importDeclaration.forceMultiLine": "whenMultiple",
+    "jsx.quoteStyle": "preferDouble",
     "lineWidth": 1000,
     "quoteStyle": "alwaysSingle",
     "trailingCommas": "never"

package/templates/default/eslint.config.mts_standalone.ejs

@@ -97,6 +97,15 @@ export default defineConfig(
       'obsidianmd/rule-custom-message': 'off'
     }
   },
+  {
+    files: typeScriptFiles,
+    rules: {
+      // The compiler already reports an undefined name, and `no-undef` cannot see ambient types and
+      // Globals a test framework declares (`describe`, `browser`, `WebdriverIO`), so typescript-eslint
+      // Advises turning it off for TypeScript.
+      'no-undef': 'off'
+    }
+  },
   {
     rules: {
       // `moment` is banned for bundle size, which does not apply here: Obsidian bundles it and

package/templates/default/jest.config.ts_framework.ejs

@@ -0,0 +1,31 @@
+import { defineObsidianPluginJestConfig } from '@mnaoumov/obsidian-dev-toolkit/test-runners/jest-config';
+
+// The toolkit's config runs ts-jest as ESM under jsdom, maps `obsidian` onto `obsidian-test-mocks` and loads
+// Both setup files. What is left here is what only this project knows.
+export default defineObsidianPluginJestConfig({
+  moduleNameMapper: {
+    // `src/main.ts` imports the stylesheet for its side effect, and jest would parse it as JavaScript.
+    '\\.(css|scss)$': '<rootDir>/scripts/stylesheet-stub.ts',
+    // Compiling a single-file component is the bundler's job, not the unit runner's. A unit test that reaches
+    // One through the plugin's module graph gets this stub instead, so the graph loads.
+    '\\.(svelte|vue)$': '<rootDir>/scripts/framework-component-stub.ts',
+    // Same decision for WebAssembly: loading a `.wasm` is the bundler's job.
+    '\\.wasm(\\?.*)?$': '<rootDir>/scripts/wasm-module-stub.ts',
+    '^data-url:': '<rootDir>/scripts/wasm-module-stub.ts',
+    // Svelte reaches its own runtime through Node subpath imports (`#client/constants`), and jest's ESM
+    // Resolver hands back the types entry for those, so the whole package goes to the stub too. It exports
+    // The `mount` / `unmount` the generated view uses.
+    '^svelte$': '<rootDir>/scripts/framework-component-stub.ts'
+  },
+  tsJestOptions: {
+    // Merged over `tsconfig.json`. `rootDir` is here rather than there because that file declares `noEmit: true`
+    // And is also read by the bundler, while ts-jest compiles WITH emit and so raises TS5011 on an inferred
+    // Common source directory.
+    tsconfig: {
+      isolatedModules: true,
+<%- render('ts-jest-tsconfig') -%>
+<%- render('lint-root-dir') -%>
+      rootDir: '.'
+    }
+  }
+});

package/templates/default/{scripts/rollup.config.ts@lint-out-dir_dev-utils.ejs → jest.config.ts_framework@lint-root-dir_framework.ejs}

@@ -1 +1 @@
-      // eslint-disable-next-line unicorn/name-replacements -- `outDir` is TypeScript's own compiler-option name.
+      // eslint-disable-next-line unicorn/name-replacements -- `rootDir` is TypeScript's own compiler-option name.

package/templates/default/jest.config.ts_framework@ts-jest-tsconfig_solid.ejs

@@ -0,0 +1,8 @@
+      // Solid compiles its JSX with `babel-preset-solid`, so the project's own tsconfig sets
+      // `jsx: 'preserve'` and leaves the JSX in place for the bundler. ts-jest has no babel step, so
+      // Preserved JSX reaches jest as `SyntaxError: Unexpected token '<'`. The automatic runtime is
+      // What ts-jest can emit on its own, and `solid-js/h` is the entry point that has one -- plain
+      // `solid-js` publishes no `jsx-runtime`. Reactivity is not compiled in, which unit tests do not
+      // Need; rendering a Solid component is an integration-test job.
+      jsx: 'react-jsx',
+      jsxImportSource: 'solid-js/h',

package/templates/default/{jest.config.ts.ejs → jest.config.ts_standalone.ejs}

@@ -46,7 +46,6 @@ const config: Config = {
     '^.+\\.tsx?$': ['ts-jest', {
       tsconfig: {
 <%- render('ts-jest-tsconfig') -%>
-<%- render('lint-root-dir') -%>
         rootDir: '.'
       },
       useESM: true

package/templates/default/package.json@targets_parcel-targets.ejs

@@ -0,0 +1,31 @@
+<%#
+  Parcel alone needs a declared target, for two reasons that both bite silently.
+
+  `"main": "main.js"` above is a Parcel TARGET as far as Parcel is concerned, with a dist directory of
+  `.` -- so `parcel build --dist-dir dist/build` wrote the bundle to the project root instead and left
+  `dist/build` holding nothing but `manifest.json`. Disabling that target is what lets `--dist-dir` apply.
+
+  The replacement target is `electron-renderer`, which is where Obsidian runs a plugin, and CommonJS.
+  Parcel counts that context as BOTH a browser and a node one, and each half is load-bearing:
+
+  - node: builtins stay external, and the resolver may exclude `obsidian` and CodeMirror, which the app
+    supplies at runtime. A plain browser target refuses outright to leave any module external.
+  - browser: package `exports` resolve the `browser` condition. A plain `node` context resolves `node`,
+    which is Solid's and Svelte's SERVER build -- a view whose `render` / `mount` never mounts anything.
+
+  `includeNodeModules` is what bundles the dependencies at all. A node-flavoured context defaults it to
+  false, which left every package a `require()` in `main.js` that nothing installs beside a plugin -- a
+  build that exited 0 and a plugin that failed to load.
+
+-%>
+  "targets": {
+    "main": false,
+    "obsidianPlugin": {
+      "context": "electron-renderer",
+      "includeNodeModules": true,
+      "isLibrary": false,
+      "optimize": true,
+      "outputFormat": "commonjs",
+      "sourceMap": false
+    }
+  },

package/templates/default/package.json@targets_parcel.ejs

@@ -1,36 +1,5 @@
-<%#
-  Parcel alone needs a declared target, for two reasons that both bite silently.
-
-  `"main": "main.js"` above is a Parcel TARGET as far as Parcel is concerned, with a dist directory of
-  `.` -- so `parcel build --dist-dir dist/build` wrote the bundle to the project root instead and left
-  `dist/build` holding nothing but `manifest.json`. Disabling that target is what lets `--dist-dir` apply.
-
-  The replacement target is `electron-renderer`, which is where Obsidian runs a plugin, and CommonJS.
-  Parcel counts that context as BOTH a browser and a node one, and each half is load-bearing:
-
-  - node: builtins stay external, and the resolver may exclude `obsidian` and CodeMirror, which the app
-    supplies at runtime. A plain browser target refuses outright to leave any module external.
-  - browser: package `exports` resolve the `browser` condition. A plain `node` context resolves `node`,
-    which is Solid's and Svelte's SERVER build -- a view whose `render` / `mount` never mounts anything.
-
-  `includeNodeModules` is what bundles the dependencies at all. A node-flavoured context defaults it to
-  false, which left every package a `require()` in `main.js` that nothing installs beside a plugin -- a
-  build that exited 0 and a plugin that failed to load.
-
-  `packageExports` makes the resolver read package `exports`. Without it, a subpath such as
-  `svelte/internal/client` does not resolve once the package is bundled rather than required.
--%>
-  "targets": {
-    "main": false,
-    "obsidianPlugin": {
-      "context": "electron-renderer",
-      "includeNodeModules": true,
-      "isLibrary": false,
-      "optimize": true,
-      "outputFormat": "commonjs",
-      "sourceMap": false
-    }
-  },
+<%# `packageExports` makes the resolver read package `exports`. Without it, a subpath such as -%>
+<%# `svelte/internal/client` does not resolve once the package is bundled rather than required. -%>
   "@parcel/resolver-default": {
     "packageExports": true
   },

package/templates/default/parcel-transformer-inline-imports.cjs.ejs

@@ -6,7 +6,7 @@
  * new bundle root unconditionally, and has no option to inline one. The other bundlers each do:
  * rollup's `inlineDynamicImports`, vite's `rollupOptions.output.inlineDynamicImports`, webpack's
  * `asyncChunks: false`. This transformer is that option for Parcel, for the same reason
- * `parcel-resolver-obsidian.cjs` is its `external` list. obsidian-dev-utils is what needs it: it
+ * `parcel-resolver-obsidian.cjs` is its `external` list. obsidian-lib is what needs it: it
  * reaches its desktop-only modules through `await import(...)`.
  *
  * It runs before Parcel's own JavaScript transformer and rewrites `import('<literal>')` into a

package/templates/default/prettier.config.mjs_framework.ejs

@@ -0,0 +1,3 @@
+import { getPrettierConfig } from '@mnaoumov/typescript-dev-toolkit/formatters/prettier';
+
+export default { ...getPrettierConfig() };

package/templates/default/scripts/build-clean.ts.ejs

@@ -1,4 +1,4 @@
-import { buildClean } from 'obsidian-dev-utils/script-utils/build';
-import { wrapCliTask } from 'obsidian-dev-utils/script-utils/cli-utils';
+import { buildClean } from '@mnaoumov/typescript-dev-toolkit/build';
+import { wrapCliTask } from '@mnaoumov/typescript-dev-toolkit/cli-utils';
 
 await wrapCliTask(() => buildClean());

package/templates/default/scripts/build-compile-typescript.ts.ejs

@@ -0,0 +1,14 @@
+import { buildCompileTypeScript } from '@mnaoumov/typescript-dev-toolkit/build';
+import { wrapCliTask } from '@mnaoumov/typescript-dev-toolkit/cli-utils';
+import { execFileSync } from 'node:child_process';
+import { createRequire } from 'node:module';
+import process from 'node:process';
+
+await wrapCliTask(async () => {
+  await buildCompileTypeScript();
+  // `src/docs` holds the Obsidian developer docs' code blocks as the docs show them, so the project's strict
+  // `tsconfig.json` leaves the folder out, and the folder's own `tsconfig.json` checks it under the official sample
+  // plugin's compiler options.
+  const tscPath = createRequire(import.meta.url).resolve('typescript/bin/tsc');
+  execFileSync(process.execPath, [tscPath, '--project', 'src/docs/tsconfig.json'], { stdio: 'inherit' });
+});

package/templates/default/scripts/build-compile.ts.ejs

@@ -1,4 +1,4 @@
-import { buildCompile } from 'obsidian-dev-utils/script-utils/build';
-import { wrapCliTask } from 'obsidian-dev-utils/script-utils/cli-utils';
+import { buildCompile } from '@mnaoumov/typescript-dev-toolkit/build';
+import { wrapCliTask } from '@mnaoumov/typescript-dev-toolkit/cli-utils';
 
 await wrapCliTask(() => buildCompile());

package/templates/default/scripts/build-options.ts.ejs

@@ -0,0 +1,9 @@
+import type { ObsidianPluginDeploymentOptions } from '@mnaoumov/obsidian-dev-toolkit/bundlers/obsidian-plugin-build';
+import type { ObsidianPluginFeatureOptions } from '@mnaoumov/obsidian-dev-toolkit/bundlers/obsidian-plugin-features';
+
+/**
+ * What obsidian-dev-toolkit builds this plugin with: its UI framework, how stylesheets are compiled, WebAssembly, and
+ * how a development build is reloaded. Every bundler adapter takes the same options, so `build` and `dev` read this one
+ * object whichever bundler runs them.
+ */
+export const buildOptions: ObsidianPluginDeploymentOptions & ObsidianPluginFeatureOptions = <%- _buildOptionsLiteral %>;

package/templates/default/scripts/build-styles.ts.ejs

@@ -1,12 +1,9 @@
 import { execSync } from 'node:child_process';
 
-// Tailwind 4 is compiled by its own CLI rather than through PostCSS, because PostCSS is not reachable on
-// Every path this generator emits: the obsidian-dev-utils presets call that library's esbuild build,
-// Which registers no PostCSS step at all AND registers `esbuild-sass-plugin` -- whose default filter is
-// `/\.(s[ac]ss|css)$/`, so it claims `.css` too -- ahead of the `customEsbuildPlugins` seam a project can
-// Add to. A PostCSS plugin appended there would never see the file. Running the CLI first sidesteps the
-// Question entirely: every bundler then receives ordinary, already-expanded CSS.
+// Tailwind 4 is compiled by its own CLI rather than through PostCSS, because not every bundler this project can
+// Use reaches PostCSS on its own. Running the CLI first means every bundler then receives ordinary,
+// Already-expanded CSS.
 //
 // `src/styles/main.css` is the SOURCE (it carries `@import "tailwindcss"`); nothing imports it directly.
 // `src/main.ts` imports the generated file below, which is git-ignored.
-execSync('npx @tailwindcss/cli --input src/styles/main.css --output src/styles/tailwind.generated.css', { stdio: 'inherit' });
+execSync('npx @tailwindcss/cli --input src/styles/main.css --output src/styles/tailwind.generated.css', { stdio: 'inherit' });

package/templates/default/scripts/build.ts.ejs

@@ -1,6 +1,6 @@
 <%# Keyed on the BUNDLER first, as the lint and format scripts are keyed on their tool. Only esbuild -%>
-<%# has a preset-specific build -- obsidian-dev-utils supplies one, and standalone inlines its own -- -%>
+<%# has a preset-specific build -- obsidian-dev-toolkit supplies one, and standalone inlines its own -- -%>
 <%# so esbuild splits again underneath and the four CLI bundlers share one script. Splitting on the -%>
-<%# preset first is what made every obsidian-dev-utils preset run esbuild whatever was chosen, while -%>
+<%# preset first is what made every toolkit preset run esbuild whatever was chosen, while -%>
 <%# still installing the chosen bundler and emitting its config for nothing to read. -%>
 <%- render('bundler') -%>

package/templates/default/scripts/build.ts@bundler_adapter-cli.ejs

@@ -0,0 +1,11 @@
+<%# vite, rollup and webpack run from their own command line, and obsidian-dev-toolkit's plugin in their config does -%>
+<%# the Obsidian part: the dist folder, the manifest, the stylesheet name and the deployment into the vault. -%>
+import { wrapCliTask } from '@mnaoumov/typescript-dev-toolkit/cli-utils';
+import { npmRun } from '@mnaoumov/typescript-dev-toolkit/npm-run';
+import { execFromRoot } from '@mnaoumov/typescript-dev-toolkit/root';
+
+await wrapCliTask(async () => {
+  // The bundler only strips the types, so the compile step checks them first.
+  await npmRun('build:compile');
+<%- render('run') -%>
+});

package/templates/default/scripts/build.ts@bundler_adapter-cli@run_rollup.ejs

@@ -0,0 +1 @@
+  await execFromRoot(['rollup', '--config', 'rollup.config.mjs'], { isInteractive: true });

package/templates/default/scripts/build.ts@bundler_adapter-cli@run_vite.ejs

@@ -0,0 +1 @@
+  await execFromRoot(['vite', 'build'], { isInteractive: true });

package/templates/default/scripts/build.ts@bundler_adapter-cli@run_webpack.ejs

@@ -0,0 +1 @@
+  await execFromRoot(['webpack', '--config', 'webpack.config.ts'], { isInteractive: true });

package/templates/default/scripts/build.ts@bundler_cli-bundler.ejs

@@ -1,5 +1,5 @@
 <%# The relative imports go in a group of their own, after a blank line, which is what an import-sorting -%>
-<%# lint rule asks for -- and the dev-utils presets now run one. Emitted only when a partial contributes. -%>
+<%# lint rule asks for -- and the framework presets now run one. Emitted only when a partial contributes. -%>
 <% const relativeImports = render('import'); -%>
 import { execSync } from 'node:child_process';
 import {

package/templates/default/scripts/build.ts@bundler_cli-bundler@import_tailwind.ejs

@@ -1,2 +1 @@
-<%- render('lint-build-styles') -%>
 import './build-styles.ts';

package/templates/default/scripts/build.ts@bundler_esbuild.ejs

@@ -1,3 +1,3 @@
-<%# obsidian-dev-utils ships an esbuild build that already handles the dist folders, the manifest copy, -%>
-<%# hot reload and the plugins-folder copy; standalone has no dev-utils and does all of that inline. -%>
+<%# obsidian-dev-toolkit ships an esbuild build that already handles the dist folders, the manifest copy, -%>
+<%# hot reload and the plugins-folder copy; standalone has no framework and does all of that inline. -%>
 <%- render('preset') -%>

package/templates/default/scripts/build.ts@bundler_esbuild@preset_framework.ejs

@@ -0,0 +1,5 @@
+import { build } from '@mnaoumov/obsidian-dev-toolkit/bundlers/esbuild';
+import { wrapCliTask } from '@mnaoumov/typescript-dev-toolkit/cli-utils';
+<%- _buildOptionsImport -%>
+
+await wrapCliTask(() => build(<%- _buildOptionsArgument %>));

package/templates/default/scripts/build.ts@bundler_parcel-adapter.ejs

@@ -0,0 +1,5 @@
+import { build } from '@mnaoumov/obsidian-dev-toolkit/bundlers/parcel';
+import { wrapCliTask } from '@mnaoumov/typescript-dev-toolkit/cli-utils';
+<%- _buildOptionsImport -%>
+
+await wrapCliTask(() => build(<%- _buildOptionsArgument %>));

package/templates/default/scripts/commit.ts_framework.ejs

@@ -0,0 +1,3 @@
+import { exec } from '@mnaoumov/typescript-dev-toolkit/exec';
+
+await exec('czg');

package/templates/default/scripts/commitlint-config.ts_framework.ejs

@@ -0,0 +1 @@
+export { commitlintConfig as config } from '@mnaoumov/typescript-dev-toolkit/commitlint-config';

package/templates/default/scripts/demo-vault-global-setup.ts.ejs

@@ -1,13 +1,13 @@
 import type { PopulateFilesParams } from 'obsidian-integration-testing';
 
+import { CODE_SCRIPT_TOOLKIT_PLUGIN_ID } from '@mnaoumov/obsidian-dev-toolkit/demo-vault-buttons';
+import { getRootFolder } from '@mnaoumov/typescript-dev-toolkit/root';
 import { join } from 'node:path';
 import process from 'node:process';
-import { CODE_SCRIPT_TOOLKIT_PLUGIN_ID } from 'obsidian-dev-utils/script-utils/demo-vault-buttons';
-import { getRootFolder } from 'obsidian-dev-utils/script-utils/root';
 import { buildDemoVaultPopulate } from 'obsidian-integration-testing';
 import { createSetup } from 'obsidian-integration-testing/vitest-global-setup-plugin';
 
-// CodeScript Toolkit is what turns a ```code-button fence into a button, and its root-relative
+// `CodeScript Toolkit` is what turns a ```code-button fence into a button, and its root-relative
 // `require('/demoSetup.ts')` into a call. In real use the in-vault `demo-vault-helper` installs it from
 // The community registry on first launch — a NETWORK step. Seeding the copy it already installed into the
 // In-repo demo vault keeps this run hermetic and independent of that bootstrap, which is why the suite
@@ -24,12 +24,15 @@ function populate(): PopulateFilesParams {
     demoVaultPath: join(getRootFolder() ?? process.cwd(), 'demo-vault'),
     injectPlugins: [{
       data: CODE_SCRIPT_TOOLKIT_SETTINGS,
+      // `demoSetup.ts` imports `@mnaoumov/obsidian-lib`, which `CodeScript Toolkit` serves only from 13.8.0, so an
+      // older copy left installed in a warm checkout is re-downloaded rather than reused.
+      minVersion: '13.8.0',
       pluginId: CODE_SCRIPT_TOOLKIT_PLUGIN_ID
     }]
   });
 }
 
-// Pre-populates the whole `demo-vault/` tree (plus the CodeScript Toolkit binary and its settings) before
+// Pre-populates the whole `demo-vault/` tree (plus the `CodeScript Toolkit` binary and its settings) before
 // Obsidian opens, so the startup scan indexes every note in one pass. Used by
 // `integration-tests:demo-vault`.
 const { setup, teardown } = createSetup({

package/templates/default/scripts/dev.ts.ejs

@@ -1,6 +1,6 @@
 <%# The twin of build.ts.ejs, and it has to be: `dev` is `build` in watch mode, so the two scripts are -%>
 <%# one decision made once. Keyed on the BUNDLER first for that reason -- keying it on the PRESET is -%>
-<%# what left every obsidian-dev-utils preset watching with esbuild whatever bundler was answered, -%>
+<%# what left every toolkit preset watching with esbuild whatever bundler was answered, -%>
 <%# while `npm run build` ran the answered one and the emitted config, loaders and plugins went unread -%>
 <%# by the path a developer actually spends the day in. -%>
 <%- render('bundler') -%>

package/templates/default/scripts/dev.ts@bundler_adapter-cli.ejs

@@ -0,0 +1,6 @@
+<%# The development build is the bundler's watch mode, which obsidian-dev-toolkit's plugin builds into `dist/dev` and -%>
+<%# deploys into the vault after every rebuild. -%>
+import { wrapCliTask } from '@mnaoumov/typescript-dev-toolkit/cli-utils';
+import { execFromRoot } from '@mnaoumov/typescript-dev-toolkit/root';
+
+<%- render('run') -%>

package/templates/default/scripts/dev.ts@bundler_adapter-cli@run_rollup.ejs

@@ -0,0 +1,3 @@
+await wrapCliTask(async () => {
+  await execFromRoot(['rollup', '--config', 'rollup.config.mjs', '--watch'], { isInteractive: true });
+});

package/templates/default/scripts/dev.ts@bundler_adapter-cli@run_vite.ejs

@@ -0,0 +1,3 @@
+await wrapCliTask(async () => {
+  await execFromRoot(['vite', 'build', '--watch'], { isInteractive: true });
+});

package/templates/default/scripts/dev.ts@bundler_adapter-cli@run_webpack.ejs

@@ -0,0 +1,3 @@
+await wrapCliTask(async () => {
+  await execFromRoot(['webpack', '--config', 'webpack.config.ts', '--watch'], { isInteractive: true });
+});

package/templates/default/scripts/dev.ts@bundler_esbuild.ejs

@@ -1,3 +1,3 @@
-<%# obsidian-dev-utils ships an esbuild `dev()` that watches, restarts on node_modules changes and -%>
-<%# re-runs build:compile; standalone has no dev-utils and its own build script is already the watcher. -%>
+<%# obsidian-dev-toolkit ships an esbuild `dev()` that watches, restarts on node_modules changes and -%>
+<%# re-runs build:compile; standalone has no framework and its own build script is already the watcher. -%>
 <%- render('preset') -%>

package/templates/default/scripts/dev.ts@bundler_esbuild@preset_framework.ejs

@@ -0,0 +1,5 @@
+import { dev } from '@mnaoumov/obsidian-dev-toolkit/bundlers/esbuild';
+import { wrapCliTask } from '@mnaoumov/typescript-dev-toolkit/cli-utils';
+<%- _buildOptionsImport -%>
+
+await wrapCliTask(() => dev(<%- _buildOptionsArgument %>));

package/templates/default/scripts/dev.ts@bundler_parcel-adapter.ejs

@@ -0,0 +1,5 @@
+import { dev } from '@mnaoumov/obsidian-dev-toolkit/bundlers/parcel';
+import { wrapCliTask } from '@mnaoumov/typescript-dev-toolkit/cli-utils';
+<%- _buildOptionsImport -%>
+
+await wrapCliTask(() => dev(<%- _buildOptionsArgument %>));

package/templates/default/scripts/eslint-config.ts.ejs

@@ -1,10 +1,10 @@
 import type { Linter } from 'eslint';
 
+import { defineEslintConfigs } from '@mnaoumov/obsidian-dev-toolkit/linters/eslint-config';
 import {
   defineConfig,
   globalIgnores
 } from 'eslint/config';
-import { defineEslintConfigs } from 'obsidian-dev-utils/script-utils/linters/eslint-config';
 
 export const configs: Linter.Config[] = defineEslintConfigs({
   customConfigs(context) {
@@ -18,7 +18,7 @@ export const configs: Linter.Config[] = defineEslintConfigs({
         '**/*.cjs',
         '**/*.js',
         '**/*.mjs',
-        'demo-vault/**'
+        'demo-vault/**'<%- render('ignores') %>
       ]),
       {
         files: context.allFiles(),
@@ -60,17 +60,6 @@ export const configs: Linter.Config[] = defineEslintConfigs({
           ]
         }
       },
-      {
-        // Two imports only a build or a bundler can resolve. `src/main.ts` imports the stylesheet
-        // `npm run build:styles` writes, which is absent until the first build and present after it -- so an
-        // Inline disable is wrong in both states, an unresolved import before and an unused directive after.
-        // `data-url:` is a parcel scheme that only parcel's own resolver knows. Both patterns are named
-        // Whether or not the answer that emits them was chosen: a pattern matching nothing costs nothing.
-        files: context.sourceFiles,
-        rules: {
-          'import-x/no-unresolved': ['error', { ignore: ['^data-url:', String.raw`tailwind\.generated\.css$`] }]
-        }
-      },
       {
         // Files whose default export is dictated from outside, the way the shared config already exempts
         // The root configs and `src/main.ts`. An ambient `declare module` describes how a `.wasm`, a CSS
@@ -99,7 +88,7 @@ export const configs: Linter.Config[] = defineEslintConfigs({
     );
   },
   editContext(context) {
-    // The shared config's root-config list is the three a plugin built on `obsidian-dev-utils` always has
+    // The shared config's root-config list is the three a plugin built on the toolkit always has
     // (`commitlint.config.ts`, `eslint.config.mts`, `vitest.config.ts`). This project may also have a root
     // Wrapper for another runner, and a root `*.ts` that ESLint reaches but no config object matches is a
     // File linted with nothing. Named unconditionally: a glob matching no emitted file costs nothing, and

package/templates/default/scripts/eslint-config.ts@ignores_docs-showcase.ejs

@@ -0,0 +1,4 @@
+,
+        // The Obsidian developer docs' code blocks, kept as the docs show them. `src/docs/tsconfig.json` type-checks
+        // Them under the official sample plugin's compiler options instead.
+        'src/docs/**'

package/templates/default/scripts/find-overexposed-fix.ts.ejs

@@ -1,13 +1,13 @@
-import process from 'node:process';
-import { parseArgs } from 'node:util';
 import {
   CliTaskResult,
   wrapCliTask
-} from 'obsidian-dev-utils/script-utils/cli-utils';
+} from '@mnaoumov/typescript-dev-toolkit/cli-utils';
 import {
   findOverExposure,
   formatOverExposureFindings
-} from 'obsidian-dev-utils/script-utils/linters/over-exposure';
+} from '@mnaoumov/typescript-dev-toolkit/linters/over-exposure';
+import process from 'node:process';
+import { parseArgs } from 'node:util';
 
 const [, , ...$arguments] = process.argv;
 

package/templates/default/scripts/find-overexposed.ts.ejs

@@ -1,12 +1,12 @@
-import process from 'node:process';
 import {
   CliTaskResult,
   wrapCliTask
-} from 'obsidian-dev-utils/script-utils/cli-utils';
+} from '@mnaoumov/typescript-dev-toolkit/cli-utils';
 import {
   findOverExposure,
   formatOverExposureFindings
-} from 'obsidian-dev-utils/script-utils/linters/over-exposure';
+} from '@mnaoumov/typescript-dev-toolkit/linters/over-exposure';
+import process from 'node:process';
 
 await wrapCliTask(() => {
   const findings = findOverExposure({ projectFolder: process.cwd() });

package/templates/default/scripts/format-check.ts@tool_biome-formatter.ejs

@@ -1,8 +1,3 @@
-import { execSync } from 'node:child_process';
-import process from 'node:process';
-
-try {
-  execSync('biome format .', { stdio: 'inherit' });
-} catch {
-  process.exit(1);
-}
+<%# The framework presets go through the toolkit runner, which takes the staged paths; standalone has no -%>
+<%# framework and shells out directly. -%>
+<%- render('preset') -%>

package/templates/default/scripts/format-check.ts@tool_biome-formatter@preset_framework.ejs

@@ -0,0 +1,7 @@
+import { wrapCliTask } from '@mnaoumov/typescript-dev-toolkit/cli-utils';
+import { format } from '@mnaoumov/typescript-dev-toolkit/formatters/biome';
+import process from 'node:process';
+
+const [, , ...paths] = process.argv;
+
+await wrapCliTask(() => format({ paths, rewrite: false }));

package/templates/default/scripts/format-check.ts@tool_biome-formatter@preset_standalone.ejs

@@ -0,0 +1,8 @@
+import { execSync } from 'node:child_process';
+import process from 'node:process';
+
+try {
+  execSync('biome format .', { stdio: 'inherit' });
+} catch {
+  process.exit(1);
+}

package/templates/default/scripts/format-check.ts@tool_dprint.ejs

@@ -1,3 +1,3 @@
-<%# The dev-utils presets go through the dev-utils runner, which resolves `dprint.json` from the repo root -%>
-<%# and falls back to the bundled one; standalone has no dev-utils and shells out directly. -%>
+<%# The framework presets go through the framework runner, which resolves `dprint.json` from the repo root -%>
+<%# and falls back to the bundled one; standalone has no framework and shells out directly. -%>
 <%- render('preset') -%>

package/templates/default/scripts/format-check.ts@tool_dprint@preset_framework.ejs

@@ -0,0 +1,7 @@
+import { format } from '@mnaoumov/obsidian-dev-toolkit/formatters/dprint';
+import { wrapCliTask } from '@mnaoumov/typescript-dev-toolkit/cli-utils';
+import process from 'node:process';
+
+const [, , ...paths] = process.argv;
+
+await wrapCliTask(() => format({ paths, rewrite: false }));

package/templates/default/scripts/format-check.ts@tool_prettier.ejs

@@ -1,8 +1,3 @@
-import { execSync } from 'node:child_process';
-import process from 'node:process';
-
-try {
-  execSync('prettier --check .', { stdio: 'inherit' });
-} catch {
-  process.exit(1);
-}
+<%# The framework presets go through the toolkit runner, which takes the staged paths; standalone has no -%>
+<%# framework and shells out directly. -%>
+<%- render('preset') -%>

package/templates/default/scripts/format-check.ts@tool_prettier@preset_framework.ejs

@@ -0,0 +1,7 @@
+import { wrapCliTask } from '@mnaoumov/typescript-dev-toolkit/cli-utils';
+import { format } from '@mnaoumov/typescript-dev-toolkit/formatters/prettier';
+import process from 'node:process';
+
+const [, , ...paths] = process.argv;
+
+await wrapCliTask(() => format({ paths, rewrite: false }));

package/templates/default/scripts/format-check.ts@tool_prettier@preset_standalone.ejs

@@ -0,0 +1,8 @@
+import { execSync } from 'node:child_process';
+import process from 'node:process';
+
+try {
+  execSync('prettier --check .', { stdio: 'inherit' });
+} catch {
+  process.exit(1);
+}

package/templates/default/scripts/format.ts@tool_biome-formatter.ejs

@@ -1,8 +1,3 @@
-import { execSync } from 'node:child_process';
-import process from 'node:process';
-
-try {
-  execSync('biome format --write .', { stdio: 'inherit' });
-} catch {
-  process.exit(1);
-}
+<%# The framework presets go through the toolkit runner, which takes the staged paths; standalone has no -%>
+<%# framework and shells out directly. -%>
+<%- render('preset') -%>

package/templates/default/scripts/format.ts@tool_biome-formatter@preset_framework.ejs

@@ -0,0 +1,7 @@
+import { wrapCliTask } from '@mnaoumov/typescript-dev-toolkit/cli-utils';
+import { format } from '@mnaoumov/typescript-dev-toolkit/formatters/biome';
+import process from 'node:process';
+
+const [, , ...paths] = process.argv;
+
+await wrapCliTask(() => format({ paths }));