Module build failed (from ./node_modules/html-loader/dist/cjs.js):

Question

I'm trying to make a quick-start for ava electron webpack and three but something went wrong in that process.

here is the repository of the project :

https://github.com/etiennerin/ecsy-three-electron-ava-quick-start

By simply trying to use my project by typing npm run dev i get the following error message :

I'm using windows.

I think the mistake might be related with my webpack-configuration which strangely seemed to work befor i tried some npm-update :

'use strict'

import { app, BrowserWindow } from 'electron'
import * as path from 'path'
import { format as formatUrl } from 'url'
import * as THREE from '../../node_modules/three/build/three.module.js';
//import {World} from '../../node_modules/ecsy/build/ecsy.module.js';

const isDevelopment = process.env.NODE_ENV !== 'production'

// global reference to mainWindow (necessary to prevent window from being garbage collected)
let mainWindow

function createMainWindow() {
  const window = new BrowserWindow({webPreferences: {nodeIntegration: true}})

  if (isDevelopment) {
    window.webContents.openDevTools()
  }

  if (isDevelopment) {
    window.loadURL(`http://localhost:${process.env.ELECTRON_WEBPACK_WDS_PORT}`)
  }
  else {
    window.loadURL(formatUrl({
      pathname: path.join(__dirname, 'index.html'),
      protocol: 'file',
      slashes: true
    }))
  }

  window.on('closed', () => {
    mainWindow = null
  })

  window.webContents.on('devtools-opened', () => {
    window.focus()
    setImmediate(() => {
      window.focus()
    })
  })

  return window
}

// quit application when all windows are closed
app.on('window-all-closed', () => {
  // on macOS it is common for applications to stay open until the user explicitly quits
  if (process.platform !== 'darwin') {
    app.quit()
  }
})

app.on('activate', () => {
  // on macOS it is common to re-create a window even after all windows have been closed
  if (mainWindow === null) {
    mainWindow = createMainWindow()
  }
})

// create main BrowserWindow when electron is ready
app.on('ready', () => {
  mainWindow = createMainWindow()
})

and my latest package.json :

{
  "name": "electron-webpack-quick-start",
  "version": "0.0.0",
  "license": "MIT",
  "scripts": {
    "start": "electron-webpack dev",
    "dev": "electron-webpack dev",
    "compile": "electron-webpack",
    "dist": "yarn compile && electron-builder",
    "dist:dir": "yarn dist --dir -c.compression=store -c.mac.identity=null",
    "test": "ava"
  },
  "dependencies": {
    "source-map-support": "^0.5.16"
  },
  "ava": {
    "files": [
      "spec/**/*"
    ],
    "require": [
      "esm"
    ]
  },
  "devDependencies": {
    "ava": "^3.5.1",
    "ecsy": "^0.2.3",
    "electron": "8.1.1",
    "electron-builder": "^22.4.1",
    "electron-webpack": "^2.7.4",
    "esm": "^3.2.25",
    "html-loader": "^1.0.0",
    "three": "^0.112.1",
    "webpack": "^4.42.0"
  }
}

Thank you very much for every piece of advice !

xdeepakv · Accepted Answer · 2020-03-22 15:45:54Z

8

Have you try to clean and reinstall

rm -rf node_modules yarn.lock package-lock.json
npm install // or yarn
run webpack

answered Mar 22, 2020 at 15:45

xdeepakv

8,1452 gold badges25 silver badges35 bronze badges

Sign up to request clarification or add additional context in comments.

3 Comments

codeanjero Over a year ago

Thank you for your help, yes i did but unfortunately it did not fix my issue, i also pulled it from github again(without all the dist,package-lock,node-modules files, same result) i don't know if this changes anything but i'm using electron-webpack but still it uses webpack in the same way as usual.

xdeepakv Over a year ago

Most prob check ur package.json version. If you use * or ^. It update with time. Try to match with package-lock.json. And fix the version in package.json

codeanjero Over a year ago

Thanks again, but still i could'nt figure out the problem, i just got back a few version on my git but this contains 2 security alerts to take into consideration , i even looked all latest version on the npm website and didn't find a viable solution

mohammad javad ahmadi · Accepted Answer · 2020-03-24 06:13:26Z

5

I also meet the same issue, but I have solved it by looking the .lock file, the html-loader now is v1.0.0[2020.3.19 updated!], Please note this is a completely rewritten loader, it is not based on html-loader-v1.0.0-alpha, so you need to add "html-loader": "1.0.0-alpha.0" to your "devDependencies" in the package.json file.

At the second you should run this command rm -rf node_module && rm -rf yarn.lock && yarn install

For more detail look at this link.

edited Mar 24, 2020 at 6:13

mohammad javad ahmadi

2,0811 gold badge14 silver badges28 bronze badges

answered Mar 24, 2020 at 1:15

championchangpeng

661 bronze badge

1 Comment

codeanjero Over a year ago

Thanks, indeed it works, but as soon as i type npm run audit fix it stops working, because there are two major security issues and 1 moderate which i'm trying to get rid of.

Addo · Accepted Answer · 2021-03-27 17:03:07Z

0

remove expose-loader from packages.json,
Remove from .lock and module

rm -rf node_modules yarn.lock

then resinstall dependencies minus expose loader

yarn install

The issue is coming from expose loader, change the configuration in the

config/webpack/environment to


const webpack = require("webpack")
environment.plugins.append("Provide", new webpack.ProvidePlugin({

  $: 'jquery',
  
  jQuery: 'jquery',
  
  Popper: ['popper.js', 'default']
  
  }))

This should work, for rails 6

answered Mar 27, 2021 at 17:03

Addo

3833 silver badges8 bronze badges

Comments

Tyler2P · Accepted Answer · 2022-04-25 17:28:24Z

0

Try this in your package.json:

Change:

"start": "react-scripts start"

To:

"start": "react-scripts --openssl-legacy-provider start"

edited Apr 25, 2022 at 17:28

Tyler2P

2,37030 gold badges26 silver badges34 bronze badges

answered Apr 25, 2022 at 16:21

sumsumcity

5575 silver badges6 bronze badges

Comments

Code Artisan · Accepted Answer · 2023-10-20 05:53:23Z

0

I also had the similar issue in a Laravel project when compiling assets. Clearing node packages and re-installing them fixed the problem. Try following commands

rm -rf node_modules package-lock.json
npm install

If you're using yarn use yarn.lock instead of package-lock.json

answered Oct 20, 2023 at 5:53

Code Artisan

11 silver badge3 bronze badges

Collectives™ on Stack Overflow

Module build failed (from ./node_modules/html-loader/dist/cjs.js):

5 Answers 5

3 Comments

1 Comment

Comments

Comments

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

5 Answers 5

3 Comments

1 Comment

Comments

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related