@mnaoumov/create-obsidian-plugin 1.0.2 → 1.2.0

package/templates/default/scripts/(build)/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)/build-compile.ts.ejs

@@ -0,0 +1,4 @@
+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)/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)/build-styles.ts.ejs

@@ -0,0 +1,9 @@
+import { execSync } from 'node:child_process';
+
+// 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' });

package/templates/default/scripts/{build.ts.ejs → (build)/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)/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)/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)/build.ts@bundler_adapter-cli@run_vite.ejs

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

package/templates/default/scripts/(build)/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)/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/(format)/format-check.ts@tool_biome-formatter.ejs

@@ -0,0 +1,3 @@
+<%# 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)/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)/format-check.ts@tool_dprint.ejs

@@ -0,0 +1,3 @@
+<%# 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)/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)/format-check.ts@tool_prettier.ejs

@@ -0,0 +1,3 @@
+<%# 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)/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)/format.ts@tool_biome-formatter.ejs

@@ -0,0 +1,3 @@
+<%# 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)/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 }));

package/templates/default/scripts/(format)/format.ts@tool_dprint.ejs

@@ -0,0 +1,3 @@
+<%# 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)/format.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 }));

package/templates/default/scripts/(format)/format.ts@tool_prettier.ejs

@@ -0,0 +1,3 @@
+<%# 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)/format.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 }));

package/templates/default/scripts/(lint)/(markdown)/lint-md-fix.ts_framework.ejs

@@ -0,0 +1,7 @@
+import { lint } from '@mnaoumov/obsidian-dev-toolkit/linters/markdownlint';
+import { wrapCliTask } from '@mnaoumov/typescript-dev-toolkit/cli-utils';
+import process from 'node:process';
+
+const [, , ...paths] = process.argv;
+
+await wrapCliTask(() => lint({ paths, shouldFix: true }));

package/templates/default/scripts/(lint)/(markdown)/lint-md.ts_framework.ejs

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

package/templates/default/scripts/{markdownlint-cli2-config.ts_dev-utils.ejs → (lint)/(markdown)/markdownlint-cli2-config.ts_framework.ejs}

@@ -1,11 +1,11 @@
-import type { MarkdownlintCli2ConfigurationSchema } from 'obsidian-dev-utils/script-utils/linters/markdownlint-types/@types/markdownlint-cli2-config-schema';
+import type { MarkdownlintCli2ConfigurationSchema } from '@mnaoumov/typescript-dev-toolkit/linters/markdownlint-types/@types/markdownlint-cli2-config-schema';
 
-import { obsidianDevUtilsConfig } from 'obsidian-dev-utils/script-utils/linters/markdownlint-cli2-config';
+import { obsidianMarkdownlintCli2Config } from '@mnaoumov/obsidian-dev-toolkit/linters/markdownlint-cli2-config';
 
 export const config: MarkdownlintCli2ConfigurationSchema = {
-  ...obsidianDevUtilsConfig,
+  ...obsidianMarkdownlintCli2Config,
   config: {
-    ...obsidianDevUtilsConfig.config,
+    ...obsidianMarkdownlintCli2Config.config,
     // Turned on here, against the shared default of off: every paragraph in this repo's markdown is one
     // physical line, and this is what stops hard wrapping from coming back. The key has to live inside
     // `config` - the spread above replaces the whole object, so a key beside it would be silently ignored.

package/templates/default/scripts/{markdownlint-cli2-config.ts_standalone.ejs → (lint)/(markdown)/markdownlint-cli2-config.ts_standalone.ejs}

@@ -8,9 +8,9 @@ import relativeLinksRule from 'markdownlint-rule-relative-links';
  * nothing else can refer to -- and an intersection is exactly where a reader wants to look one up.
  */
 interface MarkdownlintCli2Extras {
-  customRules?: unknown[];
-  globs?: string[];
-  ignores?: string[];
+  readonly customRules?: unknown[];
+  readonly globs?: string[];
+  readonly ignores?: string[];
 }
 
 export const config: MarkdownlintCli2Extras & Options = {
@@ -19,14 +19,11 @@ export const config: MarkdownlintCli2Extras & Options = {
     'default': true,
     'MD013': false,
     'MD024': {
-      // eslint-disable-next-line camelcase -- `siblings_only` is markdownlint's own option name.
       siblings_only: true
     },
     'MD052': {
-      /* eslint-disable camelcase -- `ignored_labels` and `shortcut_syntax` are markdownlint's own option names. */
       ignored_labels: ['!note', '!warning'],
       shortcut_syntax: true
-      /* eslint-enable camelcase -- `ignored_labels` and `shortcut_syntax` are markdownlint's own option names. */
     },
     'relative-links': true
   },

package/templates/default/scripts/{eslint-config.ts.ejs → (lint)/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/(lint)/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 → (lint)/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 → (lint)/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/{lint-fix.ts.ejs → (lint)/lint-fix.ts.ejs}

@@ -1,6 +1,6 @@
 <%# Keyed on the TOOL first, exactly as the format scripts are, and for the same reason. What -%>
 <%# `npm run lint:fix` runs is decided by the linter answer; only eslint has a preset-specific runner, so -%>
-<%# it splits again underneath. Splitting on the preset first is what made every obsidian-dev-utils -%>
-<%# preset emit the dev-utils ESLint runner whatever was chosen -- so `linter: biome` installed biome, -%>
+<%# it splits again underneath. Splitting on the preset first is what made every toolkit -%>
+<%# preset emit the framework ESLint runner whatever was chosen -- so `linter: biome` installed biome, -%>
 <%# emitted `biome.json`, and then ran eslint, which died looking for a config that was never written. -%>
 <%- render('tool') -%>

package/templates/default/scripts/(lint)/lint-fix.ts@tool_biome-linter.ejs

@@ -0,0 +1,3 @@
+<%# 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/(lint)/lint-fix.ts@tool_biome-linter@preset_framework.ejs

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

package/templates/default/scripts/(lint)/lint-fix.ts@tool_eslint.ejs

@@ -0,0 +1,3 @@
+<%# The toolkit presets go through the toolkit runner, which finds the config and the -%>
+<%# paths for them; standalone has no framework and shells out directly. -%>
+<%- render('preset') -%>

package/templates/default/scripts/(lint)/lint-fix.ts@tool_eslint@preset_framework.ejs

@@ -0,0 +1,7 @@
+import { lint } from '@mnaoumov/obsidian-dev-toolkit/linters/eslint';
+import { wrapCliTask } from '@mnaoumov/typescript-dev-toolkit/cli-utils';
+import process from 'node:process';
+
+const [, , ...paths] = process.argv;
+
+await wrapCliTask(() => lint({ paths, shouldFix: true }));

package/templates/default/scripts/{lint.ts.ejs → (lint)/lint.ts.ejs}

@@ -1,6 +1,6 @@
 <%# Keyed on the TOOL first, exactly as the format scripts are, and for the same reason. What -%>
 <%# `npm run lint` runs is decided by the linter answer; only eslint has a preset-specific runner, so -%>
-<%# it splits again underneath. Splitting on the preset first is what made every obsidian-dev-utils -%>
-<%# preset emit the dev-utils ESLint runner whatever was chosen -- so `linter: biome` installed biome, -%>
+<%# it splits again underneath. Splitting on the preset first is what made every toolkit -%>
+<%# preset emit the framework ESLint runner whatever was chosen -- so `linter: biome` installed biome, -%>
 <%# emitted `biome.json`, and then ran eslint, which died looking for a config that was never written. -%>
 <%- render('tool') -%>

package/templates/default/scripts/(lint)/lint.ts@tool_biome-linter.ejs

@@ -0,0 +1,3 @@
+<%# 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/(lint)/lint.ts@tool_biome-linter@preset_framework.ejs

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

package/templates/default/scripts/(lint)/lint.ts@tool_eslint.ejs

@@ -0,0 +1,3 @@
+<%# The toolkit presets go through the toolkit runner, which finds the config and the -%>
+<%# paths for them; standalone has no framework and shells out directly. -%>
+<%- render('preset') -%>

package/templates/default/scripts/(lint)/lint.ts@tool_eslint@preset_framework.ejs

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

package/templates/default/scripts/{rollup.config.ts.ejs → (rollup)/(standalone)/rollup.config.ts_standalone.ejs}

@@ -50,7 +50,7 @@ const typescript = asPluginFactory(typescriptModule);
  * compiler options, and without them TypeScript answers `undefined`. So every import in `src/` resolves
  * under the `require` condition, while a declaration file that pins `resolution-mode: import` gets the
  * ESM types. A package that ships both, such as `@codemirror/state`, is then loaded twice, and its
- * classes stop being assignable to themselves: TS2416 against obsidian-dev-utils' `StateFieldSpec`.
+ * classes stop being assignable to themselves: TS2416 against obsidian-lib's `StateFieldSpec`.
  * Handing over the `module` the emitted `tsconfig.json` declares restores the per-file mode tsc uses.
  */
 const typescriptWithResolutionModes: typeof ts = {
@@ -95,7 +95,7 @@ const EXTERNAL = [
       inlineSourceMap: !isProduction,
       inlineSources: !isProduction,
       noEmit: false,
-${render('lint-out-dir')}      outDir: distFolder,
+      outDir: distFolder,
       rewriteRelativeImportExtensions: true,
       sourceMap: !isProduction,
       typescript: typescriptWithResolutionModes
@@ -118,10 +118,10 @@ if you want to view the source, please visit the github repository of this plugi
     file: `${distFolder}/main.js`,
     format: 'cjs',
     // An Obsidian plugin is one file: the manifest names `main.js` and nothing loads a second chunk.
-    // Any dynamic import in the sources -- the obsidian-dev-utils presets have several -- otherwise
+    // Any dynamic import in the sources -- obsidian-lib, which the toolkit presets import, has several -- otherwise
     // Makes rollup refuse `output.file` and demand `output.dir`.
     inlineDynamicImports: true,
-    sourcemap: isProduction ? false : 'inline'
+    sourcemap: !isProduction && 'inline'
   },
   plugins: [
 <%- plugins.replace(/,(?<Trailing>\s*)$/, '$<Trailing>') -%>

package/templates/default/scripts/(rollup)/rollup.config.ts_framework.ejs

@@ -0,0 +1,49 @@
+import type { RollupOptions } from 'rollup';
+
+<%- sortImports(`import { obsidianPluginRollup } from '@mnaoumov/obsidian-dev-toolkit/bundlers/rollup';
+import commonjsModule from '@rollup/plugin-commonjs';
+import { nodeResolve } from '@rollup/plugin-node-resolve';
+import process from 'node:process';
+import esbuildModule from 'rollup-plugin-esbuild';
+${render('import')}`) -%>
+<%- _buildOptionsImport -%>
+
+interface DefaultExported<TDefault> {
+  default: TDefault;
+}
+
+/**
+ * A rollup plugin package's default export, as it arrives at runtime.
+ *
+ * These packages declare `export default` in CommonJS-format types, so under `module: node16` TypeScript models
+ * the default import as the module object, while at runtime it is the plugin factory. The cast follows the runtime.
+ */
+type PluginFactory<TImported> = TImported extends DefaultExported<infer TDefault> ? TDefault : TImported;
+
+function asPluginFactory<TImported>(imported: TImported): PluginFactory<TImported> {
+  return imported as PluginFactory<TImported>;
+}
+
+const commonjs = asPluginFactory(commonjsModule);
+const esbuild = asPluginFactory(esbuildModule);
+<%- render('unwrap') -%>
+
+const isProduction = !process.env['ROLLUP_WATCH'];
+
+// The rollup command line checks `input` and picks the output folder before any plugin runs, so both are named here.
+// The obsidian-dev-toolkit plugin does the rest: Obsidian's modules external, one CommonJS `main.js` with every dynamic
+// Import inlined, the stylesheet named `styles.css`, the banner and the manifest.
+export const config: RollupOptions = {
+  input: 'src/main.ts',
+  // eslint-disable-next-line unicorn/name-replacements -- `dir` is rollup's own option name.
+  output: { dir: isProduction ? 'dist/build' : 'dist/dev' },
+  plugins: [
+    obsidianPluginRollup(<%- _buildOptionsArgument %>),
+    // Strips the types without checking them, which `build:compile` does. `@rollup/plugin-typescript` calls
+    // TypeScript's JavaScript API, which TypeScript 7 no longer has.
+    esbuild({ minify: isProduction }),
+    nodeResolve({ browser: true, extensions: ['.mjs', '.js', '.json', '.ts', '.tsx'] }),
+<%- render('plugin') -%>
+    commonjs()
+  ]
+};

package/templates/default/scripts/(rollup)/rollup.config.ts_framework@import_rollup-json.ejs

@@ -0,0 +1 @@
+import jsonModule from '@rollup/plugin-json';

package/templates/default/scripts/(rollup)/rollup.config.ts_framework@import_scss.ejs

@@ -0,0 +1 @@
+import scssModule from 'rollup-plugin-scss';

package/templates/default/scripts/(rollup)/rollup.config.ts_framework@plugin_rollup-json.ejs

@@ -0,0 +1,2 @@
+    // The locale `src/i18n/index.ts` imports is JSON, which rollup reads only through this plugin.
+    json(),

package/templates/default/scripts/(rollup)/rollup.config.ts_framework@plugin_scss.ejs

@@ -0,0 +1,3 @@
+    // The toolkit compiles plain stylesheets only, so Sass is the project's own plugin. The toolkit merges what it emits
+    // Into `styles.css`.
+    scss({ fileName: 'styles.css' }),

package/templates/default/scripts/(rollup)/rollup.config.ts_framework@unwrap_rollup-json.ejs

@@ -0,0 +1 @@
+const json = asPluginFactory(jsonModule);

package/templates/default/scripts/(rollup)/rollup.config.ts_framework@unwrap_scss.ejs

@@ -0,0 +1 @@
+const scss = asPluginFactory(scssModule);

package/templates/default/scripts/(test)/(e2e)/test-e2e.ts@tool_obsidian-test.ejs

@@ -0,0 +1,2 @@
+<%# The framework presets go through the toolkit runner; standalone has no framework and shells out directly. -%>
+<%- render('preset') -%>

package/templates/default/scripts/(test)/(e2e)/test-e2e.ts@tool_obsidian-test@preset_framework.ejs

@@ -0,0 +1,4 @@
+import { testEndToEndWithObsidianTest } from '@mnaoumov/obsidian-dev-toolkit/test-runners/obsidian-test-runner';
+import { wrapCliTask } from '@mnaoumov/typescript-dev-toolkit/cli-utils';
+
+await wrapCliTask(() => testEndToEndWithObsidianTest());

package/templates/default/scripts/(test)/(e2e)/test-e2e.ts@tool_wdio-obsidian.ejs

@@ -0,0 +1,2 @@
+<%# The framework presets go through the toolkit runner; standalone has no framework and shells out directly. -%>
+<%- render('preset') -%>

package/templates/default/scripts/(test)/(e2e)/test-e2e.ts@tool_wdio-obsidian@preset_framework.ejs

@@ -0,0 +1,5 @@
+import { testEndToEndWithWdioObsidian } from '@mnaoumov/obsidian-dev-toolkit/test-runners/wdio-obsidian';
+import { wrapCliTask } from '@mnaoumov/typescript-dev-toolkit/cli-utils';
+
+// Builds the plugin first, then runs `wdio.conf.mts`.
+await wrapCliTask(() => testEndToEndWithWdioObsidian());

package/templates/default/scripts/{demo-vault-global-setup.ts.ejs → (test)/(integration)/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/(test)/(integration)/test-integration-android.ts.ejs

@@ -0,0 +1,8 @@
+import { wrapCliTask } from '@mnaoumov/typescript-dev-toolkit/cli-utils';
+import { test } from '@mnaoumov/typescript-dev-toolkit/test-runners/vitest';
+
+await wrapCliTask(() =>
+  test({
+    projects: ['integration-tests:android']
+  })
+);

package/templates/default/scripts/(test)/(integration)/test-integration-demo-vault.ts.ejs

@@ -0,0 +1,8 @@
+import { wrapCliTask } from '@mnaoumov/typescript-dev-toolkit/cli-utils';
+import { test } from '@mnaoumov/typescript-dev-toolkit/test-runners/vitest';
+
+await wrapCliTask(() =>
+  test({
+    projects: ['integration-tests:demo-vault']
+  })
+);

package/templates/default/scripts/(test)/(integration)/test-integration-desktop-performance.ts.ejs

@@ -0,0 +1,8 @@
+import { wrapCliTask } from '@mnaoumov/typescript-dev-toolkit/cli-utils';
+import { test } from '@mnaoumov/typescript-dev-toolkit/test-runners/vitest';
+
+await wrapCliTask(() =>
+  test({
+    projects: ['integration-tests:desktop-performance']
+  })
+);

package/templates/default/scripts/(test)/(integration)/test-integration-desktop.ts.ejs

@@ -0,0 +1,8 @@
+import { wrapCliTask } from '@mnaoumov/typescript-dev-toolkit/cli-utils';
+import { test } from '@mnaoumov/typescript-dev-toolkit/test-runners/vitest';
+
+await wrapCliTask(() =>
+  test({
+    projects: ['integration-tests:desktop']
+  })
+);

package/templates/default/scripts/(test)/(integration)/test-integration-no-app.ts.ejs

@@ -0,0 +1,8 @@
+import { wrapCliTask } from '@mnaoumov/typescript-dev-toolkit/cli-utils';
+import { test } from '@mnaoumov/typescript-dev-toolkit/test-runners/vitest';
+
+await wrapCliTask(() =>
+  test({
+    projects: ['integration-tests:no-app']
+  })
+);