You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
(node:14304) UnhandledPromiseRejectionWarning: ReferenceError: performance is not defined
at initTSConfckParseOptions (file:///D:/git/data-bind-dom/node_modules/vite/dist/node/chunks/dep-e8f070e8.js:14042:29)
at initTSConfck (file:///D:/git/data-bind-dom/node_modules/vite/dist/node/chunks/dep-e8f070e8.js:14033:28)
at esbuildPlugin (file:///D:/git/data-bind-dom/node_modules/vite/dist/node/chunks/dep-e8f070e8.js:13850:5)
at resolvePlugins (file:///D:/git/data-bind-dom/node_modules/vite/dist/node/chunks/dep-e8f070e8.js:42295:36)
at resolveConfig (file:///D:/git/data-bind-dom/node_modules/vite/dist/node/chunks/dep-e8f070e8.js:64242:30)
at async _createServer (file:///D:/git/data-bind-dom/node_modules/vite/dist/node/chunks/dep-e8f070e8.js:63274:20)
at async CAC. (file:///D:/git/data-bind-dom/node_modules/vite/dist/node/cli.js:733:24)
(Use node --trace-warnings ... to show where the warning was created)
(node:14304) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of
an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 2)
(node:14304) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that
are not handled will terminate the Node.js process with a non-zero exit code.
Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead.
Are you using the latest version of vscode? vscode uses it's bundled TypeScript by default, which may not be typescript v5 as required by the template. You can also configure vscode to use your project's (workspace) typescript version.
Describe the bug
Just now, I generated a empty vanilla-ts project.
Reproduction
https://github.com/hezedu/SomethingBoring/tree/master/vite-issues
Steps to reproduce
npm create vite@latest
chose
vanilla
andtypescript
.npm install
.open the project with VS Code and see the 4 problems.
System Info
Used Package Manager
npm
Logs
(node:14304) UnhandledPromiseRejectionWarning: ReferenceError: performance is not defined
at initTSConfckParseOptions (file:///D:/git/data-bind-dom/node_modules/vite/dist/node/chunks/dep-e8f070e8.js:14042:29)
at initTSConfck (file:///D:/git/data-bind-dom/node_modules/vite/dist/node/chunks/dep-e8f070e8.js:14033:28)
at esbuildPlugin (file:///D:/git/data-bind-dom/node_modules/vite/dist/node/chunks/dep-e8f070e8.js:13850:5)
at resolvePlugins (file:///D:/git/data-bind-dom/node_modules/vite/dist/node/chunks/dep-e8f070e8.js:42295:36)
at resolveConfig (file:///D:/git/data-bind-dom/node_modules/vite/dist/node/chunks/dep-e8f070e8.js:64242:30)
at async _createServer (file:///D:/git/data-bind-dom/node_modules/vite/dist/node/chunks/dep-e8f070e8.js:63274:20)
at async CAC. (file:///D:/git/data-bind-dom/node_modules/vite/dist/node/cli.js:733:24)
(Use
node --trace-warnings ...
to show where the warning was created)(node:14304) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of
an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag
--unhandled-rejections=strict
(see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 2)(node:14304) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that
are not handled will terminate the Node.js process with a non-zero exit code.
Validations
The text was updated successfully, but these errors were encountered: