Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

New `mix.js` file

See original GitHub issue

What exactly is the the new mix.js file used for? Do I need it? Can I turn it off?

webpackJsonp([6],{

/***/ 113:
/***/ (function(module, exports) {

// removed by extract-text-webpack-plugin

/***/ }),

/***/ 114:
/***/ (function(module, exports) {

// removed by extract-text-webpack-plugin

/***/ }),

/***/ 115:
/***/ (function(module, exports) {

// removed by extract-text-webpack-plugin

/***/ }),

/***/ 116:
/***/ (function(module, exports) {



/***/ }),

/***/ 320:
/***/ (function(module, exports, __webpack_require__) {

__webpack_require__(116);
__webpack_require__(114);
__webpack_require__(115);
module.exports = __webpack_require__(113);


/***/ })

},[320]);

Issue Analytics

State:
Created 6 years ago
Reactions:1
Comments:12 (6 by maintainers)

Top GitHub Comments

8reactions

sweetrollcommented, May 3, 2017

This issue is still in 0.11.4 but seems to disappear if the js config is put above the sass.

0reactions

zishanjcommented, Jul 23, 2017

In my case, I am using latest laravel-mix version 1.3. My mix.js file is automatically deleted as mentioned by @JeffreyWay but then it throws the error:

Error: ENOENT: no such file or directory, open ‘/src/app/public/js/mix.js’ at Error (native) at Object.fs.openSync (fs.js:641:18) at Object.fs.readFileSync (fs.js:509:33) at File.read (/src/node_modules/laravel-mix/src/File.js:180:19) at File.version (/src/node_modules/laravel-mix/src/File.js:190:25) at Manifest.hash (/src/node_modules/laravel-mix/src/Manifest.js:55:65)

and I can see entry of mix.js file in mix-manifest.json file but the file is automatically deleted.