manifest.js is not created in the same folder as vendor.js
See original GitHub issue- Laravel Mix Version: 1.4.2
- Node Version (
node -v
): v6.10.3 - NPM Version (
npm -v
): 3.10.10 - OS: OSX
Description:
After upgrading to Laravel Mix 1.4.2 from 0.11.4, manifest.js
is not created in the same folder as vendor.js
. Instead, manifest.js
was added to the folder where a javascript is built by js()
function.
Steps To Reproduce:
webpack.mix.js:
mix.setPublicPath('app/public')
.js('asset/js/test/test.js', 'js/test')
.extract(['vue'], 'js/vendor.js');
webpack output:
/js/vendor.js 82.4 kB 0 [emitted] /js/vendor
/js/test/test.js 72 bytes 1 [emitted] /js/test/test
/js/test/manifest.js 1.38 kB 2 [emitted] /js/test/manifest
I believe it was /js/manifest.js
instead of /js/test/manifest.js
in Laravel Mix 0.11.4.
Issue Analytics
- State:
- Created 6 years ago
- Reactions:18
- Comments:14
Top Results From Across the Web
manifest.js is not created in the same folder as vendor.js #1118
js is not created in the same folder as vendor.js . Instead, manifest.js was added to the folder where a javascript is built...
Read more >Rails asset pipeline: Standard way for including all /vendor ...
I know it's an old question, but you can create a manifest file on the vender/assets/javascript folder ...
Read more >Versioning with Mix, manifest does not exist. {but.... it does!)
so when I call it in my view, I get an error that it cant find the file, but if I create a...
Read more >Entry Points - webpack
Do not create an entry for vendors or other stuff that is not the starting point of execution. Multi-Page Application. webpack.config.js module.exports =...
Read more >Compiling Assets (Mix) - The PHP Framework For Web Artisans
One potential downside to bundling all of your application-specific JavaScript with your vendor libraries such as React and Vue is that it makes...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
This issue should be re-opened.
I found a workaround for this issue by creating an empty js file in
js/empty.js
and doing this:webpack output: