Closed Miosame closed 3 years ago
I think you need the runtime version.
Add this to mix file
mix.webpackConfig({
resolve: {
alias: {
'vue$': 'vue/dist/vue.esm-bundler.js' // or 'vue' : '...'
},
},
})
I suggest to use Laravel Mix v6, I'll archive this repo soon.
@KABBOUCHI v6 isn't yet tagged nor announced a release date, are you referring to the beta releases?
As mentioned by Kabbouchi, just use beta-v6 of laravel-mix together with: js(...).vue()
@Miosame could you please show me an example? I get the error:
[webpack-cli] Unknown argument: --no-progress
[webpack-cli] Unknown argument: --hide-modules
? Which flags do you want to use? …
✔ --entry: The entry point(s) of your application e.g. ./src/main.js
✔ --config: Provide path to a webpack configuration file e.g. ./webpack.config.js
✔ --color: Enable/Disable colors on console
...... etc.
My settings are:
const mix = require('laravel-mix');
mix.js('demo/resources/js/app.js', 'demo/public/js/app.js').vue();
with npm "laravel-mix": "github:JeffreyWay/laravel-mix#v6.0.0-beta.10",
@pmochine you need to remove --no-progress
and --hide-modules
from iirc the package.json
, they are incompatible with newer versions.
Similar to #5 - however it does not work as described.
my blade template is essentially:
test.vue:
app.js:
webpack.mix.js:
When I visit the blade template, it replaces all contents of #app with:
My package.json after the readme dependencies:
what am I missing or is this a laravel mix bug? (similar to #9 ?)
Thanks!