From b9fcf9326d71e3d15682b6301c11ec2d3b831d06 Mon Sep 17 00:00:00 2001 From: typescript-bot Date: Sat, 16 Jan 2021 07:25:40 +0000 Subject: [PATCH 1/2] Update user baselines +cc @sandersn --- tests/baselines/reference/docker/vue-next.log | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/tests/baselines/reference/docker/vue-next.log b/tests/baselines/reference/docker/vue-next.log index f790e8d748b79..4fe0fbe65dbe6 100644 --- a/tests/baselines/reference/docker/vue-next.log +++ b/tests/baselines/reference/docker/vue-next.log @@ -26,6 +26,7 @@ Writing: /vue-next/temp/compiler-ssr.api.json The API report is up to date: temp/compiler-ssr.api.md Writing package typings: /vue-next/packages/compiler-ssr/dist/compiler-ssr.d.ts Writing package typings: /vue-next/dist/compiler-ssr.d.ts +API Extractor completed successfully. Rolling up type definitions for compiler-sfc... Analysis will use the bundled TypeScript version 4.1.3 *** The target project appears to use TypeScript X.X.X-insiders.xxxxxxxx which is newer than the bundled compiler engine; consider upgrading API Extractor. @@ -34,7 +35,6 @@ The API report is up to date: temp/compiler-sfc.api.md Writing package typings: /vue-next/packages/compiler-sfc/dist/compiler-sfc.d.ts Writing package typings: /vue-next/dist/compiler-sfc.d.ts API Extractor completed successfully. -API Extractor completed successfully. @@ -75,9 +75,9 @@ Warning: dist/packages/compiler-core/src/options.d.ts:149:35 - (tsdoc-malformed- Warning: dist/packages/compiler-core/src/options.d.ts:149:36 - (tsdoc-malformed-inline-tag) Expecting a TSDoc tag starting with "{@" /vue-next/packages/compiler-sfc/src/index.ts → packages/compiler-sfc/dist/compiler-sfc.cjs.js... created packages/compiler-dom/dist/compiler-dom.global.prod.js in ?s -/vue-next/packages/compiler-ssr/src/index.ts → packages/compiler-ssr/dist/compiler-ssr.cjs.js... created packages/compiler-sfc/dist/compiler-sfc.cjs.js in ?s /vue-next/packages/compiler-sfc/src/index.ts → packages/compiler-sfc/dist/compiler-sfc.global.js... +/vue-next/packages/compiler-ssr/src/index.ts → packages/compiler-ssr/dist/compiler-ssr.cjs.js... created packages/compiler-ssr/dist/compiler-ssr.cjs.js in ?s (!) Missing shims for Node.js built-ins Creating a browser bundle that depends on 'path', 'url' and 'util'. You might need to include https://github.com/ionic-team/rollup-plugin-node-polyfills @@ -116,13 +116,13 @@ Error: /vue-next/packages/reactivity/src/baseHandlers.ts(192,3): semantic error /vue-next/node_modules/brotli/build/encode.js:3 1 Date: Sun, 17 Jan 2021 03:11:06 +0000 Subject: [PATCH 2/2] Update user baselines --- tests/baselines/reference/docker/vue-next.log | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/tests/baselines/reference/docker/vue-next.log b/tests/baselines/reference/docker/vue-next.log index 4fe0fbe65dbe6..e9c60afa5eaf6 100644 --- a/tests/baselines/reference/docker/vue-next.log +++ b/tests/baselines/reference/docker/vue-next.log @@ -19,14 +19,6 @@ The API report is up to date: temp/compiler-dom.api.md Writing package typings: /vue-next/packages/compiler-dom/dist/compiler-dom.d.ts Writing package typings: /vue-next/dist/compiler-dom.d.ts API Extractor completed successfully. -Rolling up type definitions for compiler-ssr... -Analysis will use the bundled TypeScript version 4.1.3 -*** The target project appears to use TypeScript X.X.X-insiders.xxxxxxxx which is newer than the bundled compiler engine; consider upgrading API Extractor. -Writing: /vue-next/temp/compiler-ssr.api.json -The API report is up to date: temp/compiler-ssr.api.md -Writing package typings: /vue-next/packages/compiler-ssr/dist/compiler-ssr.d.ts -Writing package typings: /vue-next/dist/compiler-ssr.d.ts -API Extractor completed successfully. Rolling up type definitions for compiler-sfc... Analysis will use the bundled TypeScript version 4.1.3 *** The target project appears to use TypeScript X.X.X-insiders.xxxxxxxx which is newer than the bundled compiler engine; consider upgrading API Extractor. @@ -35,6 +27,14 @@ The API report is up to date: temp/compiler-sfc.api.md Writing package typings: /vue-next/packages/compiler-sfc/dist/compiler-sfc.d.ts Writing package typings: /vue-next/dist/compiler-sfc.d.ts API Extractor completed successfully. +Rolling up type definitions for compiler-ssr... +Analysis will use the bundled TypeScript version 4.1.3 +*** The target project appears to use TypeScript X.X.X-insiders.xxxxxxxx which is newer than the bundled compiler engine; consider upgrading API Extractor. +Writing: /vue-next/temp/compiler-ssr.api.json +The API report is up to date: temp/compiler-ssr.api.md +Writing package typings: /vue-next/packages/compiler-ssr/dist/compiler-ssr.d.ts +Writing package typings: /vue-next/dist/compiler-ssr.d.ts +API Extractor completed successfully. @@ -78,7 +78,6 @@ created packages/compiler-dom/dist/compiler-dom.global.prod.js in ?s created packages/compiler-sfc/dist/compiler-sfc.cjs.js in ?s /vue-next/packages/compiler-sfc/src/index.ts → packages/compiler-sfc/dist/compiler-sfc.global.js... /vue-next/packages/compiler-ssr/src/index.ts → packages/compiler-ssr/dist/compiler-ssr.cjs.js... -created packages/compiler-ssr/dist/compiler-ssr.cjs.js in ?s (!) Missing shims for Node.js built-ins Creating a browser bundle that depends on 'path', 'url' and 'util'. You might need to include https://github.com/ionic-team/rollup-plugin-node-polyfills (!) Missing global variable names @@ -87,6 +86,7 @@ path (guessing 'path') url (guessing 'url') util (guessing 'require$$0') created packages/compiler-sfc/dist/compiler-sfc.global.js in ?s +created packages/compiler-ssr/dist/compiler-ssr.cjs.js in ?s Warning: dist/packages/compiler-sfc/src/compileScript.d.ts:27:36 - (tsdoc-escape-greater-than) The ">" character should be escaped using a backslash to avoid confusion with an HTML tag Warning: dist/packages/compiler-sfc/src/compileScript.d.ts:27:23 - (tsdoc-html-tag-missing-equals) The HTML element has an invalid attribute: Expecting "=" after HTML attribute name Warning: dist/packages/compiler-sfc/src/compileStyle.d.ts:18:8 - (tsdoc-missing-deprecation-message) The @deprecated block must include a deprecation message, e.g. describing the recommended alternative