@poveste/plugin-vue 0.20.0 → 0.21.0

package/src/util/project-vue.ts

@@ -0,0 +1,13 @@
+import { readFileSync } from 'node:fs'
+import { createRequire } from 'node:module'
+import { join } from 'node:path'
+
+export function projectVueVersion(root: string): string | undefined {
+  try {
+    const manifest = createRequire(join(root, 'package.json')).resolve('vue/package.json')
+    return JSON.parse(readFileSync(manifest, 'utf8')).version
+  }
+  catch {
+    return undefined
+  }
+}

package/testing.d.ts

@@ -0,0 +1,2 @@
+// https://github.com/microsoft/TypeScript/issues/33079
+export * from './dist/testing/index'

package/dist/docgen/typescript.d.ts

@@ -1,9 +0,0 @@
-/** The version of the first `typescript` found in `dirs`, searched in order as Node searches `node_modules`. */
-export declare function typescriptVersionIn(dirs: string[]): string | undefined;
-/** Why auto-docs cannot read a Vue component's types with the TypeScript in `dirs`, or nothing when it can. */
-export declare function typescriptProblemIn(dirs: string[]): string | undefined;
-/**
- * The same question for the TypeScript `vue-component-meta` will load: it requires
- * `typescript` from where it is installed, an optional peer that npm does not add.
- */
-export declare function typescriptProblem(): string | undefined;

package/dist/docgen/typescript.js

@@ -1,36 +0,0 @@
-import { existsSync, readFileSync } from 'node:fs';
-import { createRequire } from 'node:module';
-import { join } from 'pathe';
-// `vue-component-meta` 3.3 calls `ts.readJsonConfigFile`, which TypeScript 7 no
-// longer has, and no release of it reads TypeScript 7 yet (#1382).
-const NEWEST_MAJOR = 6;
-const FIX = 'Install `typescript@6` in the book to turn it on, or set `autoDocs: false` to turn it off without this message.';
-/** The version of the first `typescript` found in `dirs`, searched in order as Node searches `node_modules`. */
-export function typescriptVersionIn(dirs) {
-    for (const dir of dirs) {
-        const manifest = join(dir, 'typescript', 'package.json');
-        if (existsSync(manifest)) {
-            return JSON.parse(readFileSync(manifest, 'utf8')).version;
-        }
-    }
-    return undefined;
-}
-/** Why auto-docs cannot read a Vue component's types with the TypeScript in `dirs`, or nothing when it can. */
-export function typescriptProblemIn(dirs) {
-    const version = typescriptVersionIn(dirs);
-    if (!version) {
-        return `Auto-docs is off: it reads component types with TypeScript, which this book does not have. ${FIX}`;
-    }
-    if (Number.parseInt(version, 10) > NEWEST_MAJOR) {
-        return `Auto-docs is off: it reads component types with TypeScript ${NEWEST_MAJOR} or earlier, and this book has TypeScript ${version}. ${FIX}`;
-    }
-    return undefined;
-}
-/**
- * The same question for the TypeScript `vue-component-meta` will load: it requires
- * `typescript` from where it is installed, an optional peer that npm does not add.
- */
-export function typescriptProblem() {
-    const meta = createRequire(import.meta.url).resolve('vue-component-meta');
-    return typescriptProblemIn(createRequire(meta).resolve.paths('typescript') ?? []);
-}

package/src/docgen/typescript.ts

@@ -1,41 +0,0 @@
-import { existsSync, readFileSync } from 'node:fs'
-import { createRequire } from 'node:module'
-import { join } from 'pathe'
-
-// `vue-component-meta` 3.3 calls `ts.readJsonConfigFile`, which TypeScript 7 no
-// longer has, and no release of it reads TypeScript 7 yet (#1382).
-const NEWEST_MAJOR = 6
-
-const FIX = 'Install `typescript@6` in the book to turn it on, or set `autoDocs: false` to turn it off without this message.'
-
-/** The version of the first `typescript` found in `dirs`, searched in order as Node searches `node_modules`. */
-export function typescriptVersionIn(dirs: string[]): string | undefined {
-  for (const dir of dirs) {
-    const manifest = join(dir, 'typescript', 'package.json')
-    if (existsSync(manifest)) {
-      return JSON.parse(readFileSync(manifest, 'utf8')).version
-    }
-  }
-  return undefined
-}
-
-/** Why auto-docs cannot read a Vue component's types with the TypeScript in `dirs`, or nothing when it can. */
-export function typescriptProblemIn(dirs: string[]): string | undefined {
-  const version = typescriptVersionIn(dirs)
-  if (!version) {
-    return `Auto-docs is off: it reads component types with TypeScript, which this book does not have. ${FIX}`
-  }
-  if (Number.parseInt(version, 10) > NEWEST_MAJOR) {
-    return `Auto-docs is off: it reads component types with TypeScript ${NEWEST_MAJOR} or earlier, and this book has TypeScript ${version}. ${FIX}`
-  }
-  return undefined
-}
-
-/**
- * The same question for the TypeScript `vue-component-meta` will load: it requires
- * `typescript` from where it is installed, an optional peer that npm does not add.
- */
-export function typescriptProblem(): string | undefined {
-  const meta = createRequire(import.meta.url).resolve('vue-component-meta')
-  return typescriptProblemIn(createRequire(meta).resolve.paths('typescript') ?? [])
-}