During my project using Vite, I encountered an error when running npm run dev, displaying the message:
Failed to scan for dependencies from entries: <path>/Learning/Vite-test/index.html[ERROR] No loader is configured for ".html" files: index.htmlThis issue appears to be unique to my situation as I have not found any relevant solutions through research, despite being a beginner in this area.
My attempted solution involved installing and adding the html loader to the Vite configuration file, but unfortunately, it did not resolve the error.
Below is a snippet of my Vite configuration file:
import { fileURLToPath, URL } from 'node:url'
import { defineConfig } from 'vite'
import vue from '@vitejs/plugin-vue'
// https://vitejs.dev/config/
export default defineConfig({
plugins: [
vue(),
],
resolve: {
alias: {
'@': fileURLToPath(new URL('./src', import.meta.url))
},
resolve: {
extensions: ['.js', '.ts', '.vue', '.json', '.html'],
},
module: {
rules: [
{
test: /\.html$/i,
loader: 'html-loader',
},
],
},
}
})
A similar error also arises when creating projects with Vue/cli, which gives me the following message:
Compiling...
ERROR Failed to compile with 1 error 8:24:19 PM
error
Module not found: Error: Can't resolve '<path>\learn-vuetify\node_modules\webpack-dev-server\client\index.js?protocol=ws&hostname=192.168.8.106&port=8080&pathname=%2Fws&logging=none&progress=true&overlay=%7B%22errors%22%3Atrue%2C%22warnings%22%3Afalse%7D&reconnect=10&hot=true&live-reload=true' in '<path>\learn-vuetify'
ERROR in Module not found: Error: Can't resolve '<path>\learn-vuetify\node_modules\webpack-dev-server\client\index.js?protocol=ws&hostname=192.168.8.106&port=8080&pathname=%2Fws&logging=none&progress=true&overlay=%7B%22errors%22%3Atrue%2C%22warnings%22%3Afalse%7D&reconnect=10&hot=true&live-reload=true' in '<path>\learn-vuetify'
webpack compiled with 1 error
To address these issues, I have considered several possibilities:
- Potential local security settings on Windows might be causing this.
- An error may have occurred during the installation of Node.
- There could be corrupted dependencies at play, although this seems rare as no similar cases have been reported.
I am still unsure of the root cause of these errors and would greatly appreciate any insights or assistance!