fix: workaround for possible Vite bug

vitejs/vite#5086
Uninen · Sep 25, 2021 · 2aee7b2 · 2aee7b2 · vercel · Sep 25, 2021
1 parent aadb4b8
commit 2aee7b2
Show file tree

Hide file tree

Showing 3 changed files with 8 additions and 6 deletions.
diff --git a/src/env.d.ts b/src/env.d.ts
@@ -1,4 +1,11 @@
 /// <reference types="vite/client" />
+
+declare module '*.vue' {
+  import { DefineComponent } from 'vue'
+  // eslint-disable-next-line @typescript-eslint/no-explicit-any, @typescript-eslint/ban-types
+  const component: DefineComponent<{}, {}, any>
+  export default component
+}
 interface ImportMetaEnv {
   readonly VITE_APP_VERSION: string
   readonly VITE_APP_BUILD_EPOCH: number

diff --git a/src/pages/Index.vue b/src/pages/Index.vue
@@ -76,7 +76,7 @@
     <h3>Typed ENV Variables</h3>
 
     <p>
-      Vite exposes a special <code>import.meta.env</code> object for ENV variables (see
+      Vite exposes a special <code>meta.env</code> object for ENV variables (see
       <a href="https://vitejs.dev/guide/env-and-mode.html">official docs</a>). This template extends
       that object and adds custom typed variables which you can easily use and modify to your needs.
     </p>

diff --git a/src/shims-vue.d.ts b/src/shims-vue.d.ts