Hello,

If we use this package and run npm update to update dependencies we get this new error:
EventSource's response has a MIME type ("text/html") that is not "text/event-stream". Aborting the connection.
This problem seems to be coming from axios because npm update @nuxtjs/axios is giving the error.
Something might have changed, did you get info on this @mentAl-maZe ?

Gautier

The system generates a client and server on localhost.
If I call up e.g. http://example.com via my domain, then I get to the Laravel start page instead of the (SSR) Nuxt page.

If I add example.com/app/ to my domain, it will be linked to /public/spa.html. But I don't want that. The aim is with the call:
http://example.com the (SSR) nuxt page is loaded. Can you please give me a little help.
best regards
Dieter

Thread to discuss properties and requirements for future LaraNuxt releases

Hello,

It happens that the dev environment is crashing using npm run dev
It can happen once for 2 jours straight coding. This is pretty old but I tought this was temporary. This is coming from the changes you made @mentAl-maZe when adding new functionnalities 😃

Couldn't get log since the node script is freezing, will try the next time it happens to get something out of it

Gautier

Hey Guys,

I'm using latest LaraNuxt and got error like this:

I'm running it on Docker.

1. Clone this repo.
2. composer install , php artisan key:generate , npm install and npm run build .
3. Access to http://localhost/app .

I don't use "serve" for production operation.

Unfortunately, I cannot use the laravel functionality in the backend either. No DB queries or inserts possible. After compiling the software writes "Laravel support disabled" that is to blame, if so, where can I activate laravel.
With best regards
Dieter

Hello,

Actually using this package with the base path ('/' instead of '/app') is making problems:

• On dev the entire public file is deleted as intended to clear all nuxt stuff (removing robots / etc) (I found a bypass but can't remember how)
• All nuxt files are disposed in the public folder and can make conflict with other files from laravel mix for example

I think it would be great forcing the app by default being at '/' because it seems more common.

Hey Guys,

I noticed this has been worked on for a year or more, but only recently have created a release version. I 'm down to use a template to help Laravel and Nuxt work together, but I noticed, you'r composer requirement uses another package of yours called "laravel-nuxt", which makes me think this is bigger than just a skeleton template for both frameworks. Assuming you guys are committed to making this work long term, can you explain what the "laravel-nuxt" package does to make this template function?

Looking very promising and cant wait to test it out!

I think we should mention that this repository is a template to allow all posibilities given by this option:
https://docs.github.com/en/github/creating-cloning-and-archiving-repositories/creating-a-template-repository

clone repository, install dependencies and npm run dev, Listening: in http: // localhost: 3000 / app / and show server error

vagrant@homestead:~/samosbor$ npm run dev

@ dev /home/vagrant/samosbor
npm run mix:dev && npm run nuxt:dev

@ mix:dev /home/vagrant/samosbor
cross-env NODE_ENV=development node_modules/webpack/bin/webpack.js --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js

sh: 1: cross-env: not found
npm ERR! code ELIFECYCLE
npm ERR! syscall spawn
npm ERR! file sh
npm ERR! errno ENOENT
npm ERR! @ mix:dev: cross-env NODE_ENV=development node_modules/webpack/bin/webpack.js --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the @ mix:dev script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR! /home/vagrant/.npm/_logs/2020-06-21T12_26_19_577Z-debug.log
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! @ dev: npm run mix:dev && npm run nuxt:dev
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the @ dev script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR! /home/vagrant/.npm/_logs/2020-06-21T12_26_19_591Z-debug.log

vagrant@homestead:~/samosbor$ cat /home/vagrant/.npm/_logs/2020-06-21T12_26_19_591Z-debug.log
0 info it worked if it ends with ok
1 verbose cli [ '/usr/bin/node', '/usr/bin/npm', 'run', 'dev' ]
2 info using [email protected]
3 info using [email protected]
4 verbose run-script [ 'predev', 'dev', 'postdev' ]
5 info lifecycle @~predev: @
6 info lifecycle @~dev: @
7 verbose lifecycle @~dev: unsafe-perm in lifecycle true
8 verbose lifecycle @~dev: PATH: /usr/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/home/vagrant/samosbor/node_modules/.bin:/home/vagrant/.composer/vendor/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
9 verbose lifecycle @~dev: CWD: /home/vagrant/samosbor
10 silly lifecycle @~dev: Args: [ '-c', 'npm run mix:dev && npm run nuxt:dev' ]
11 silly lifecycle @~dev: Returned: code: 1 signal: null
12 info lifecycle @~dev: Failed to exec dev script
13 verbose stack Error: @ dev: npm run mix:dev && npm run nuxt:dev
13 verbose stack Exit status 1
13 verbose stack at EventEmitter. (/usr/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:332:16)
13 verbose stack at EventEmitter.emit (events.js:315:20)
13 verbose stack at ChildProcess. (/usr/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
13 verbose stack at ChildProcess.emit (events.js:315:20)
13 verbose stack at maybeClose (internal/child_process.js:1051:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:287:5)
14 verbose pkgid @
15 verbose cwd /home/vagrant/samosbor
16 verbose Linux 5.4.0-37-generic
17 verbose argv "/usr/bin/node" "/usr/bin/npm" "run" "dev"
18 verbose node v14.4.0
19 verbose npm v6.14.5
20 error code ELIFECYCLE
21 error errno 1
22 error @ dev: npm run mix:dev && npm run nuxt:dev
22 error Exit status 1
23 error Failed at the @ dev script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]

Homestead, vagrant, virtualbox - last version.