gymdone

Do the front and backend have to be developed and run from the same directory?

Does this mean that I would have to use Nova thru an axios /api/ call from my SPA and write my own UX/UI ?

Right, but how do my front-end users access Nova? Can they?

But if I use http://myvueapp.com/login -- vue router will let me log in.

But if I use http://myvueapp.com/nova -- I will 404 because Nova is not installed here, it's over on the backend !?!

Do I understand this correctly?

OK, given a Vue SPA project with vue-router in it's own directory, say /front and a Laravel project in it's own directory, say /back

I understand how Vue can route to login.vue and register.vue and say, products.vue and how they can axios to the /routes/api.php router.

But, they seem so separate and independent. We want Nova available to our developers and admin folks and a given subset of Nova available to customer team administrators. With Nova installed on the /back, it won't be available via the Vue router in the /front, so... Nova is more important to us than the SPA, so I guess I have to ditch the SPA idea......true?

Yes, VS Code !! When I open a Bash shell in Ubuntu 20 WSL2 and enter

$ code .

The WSL folks include in the Linux path: /mnt/c/Program Files/Microsoft VS Code/bin

So vscode runs and on the first run it automatically enables it's Remote-WSL mode! VS Code stays actually running under windows but seamlessly remotes into WSL where the files are stored and run. I'm using Windows Terminal Preview 1.2.2 and using Bash into WSL and I configured the terminal inside of vscode to run the same!

All works just great!

This just started happening ...

~/STGdev/lvvn $ npm run watch

> @ watch /home/gymdo/STGdev/lvvn
> npm run development -- --watch


> @ development /home/gymdo/STGdev/lvvn
> cross-env NODE_ENV=development node_modules/webpack/bin/webpack.js --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js "--watch"

10% building 1/1 modules 0 active
webpack is watching the files…

98% after emitting SizeLimitsPlugin

 ERROR  Failed to compile with 1 errors                                                                                  10:22:54 PM

 error  in ./resources/sass/app.scss

Module build failed (from ./node_modules/css-loader/dist/cjs.js):
TypeError: text.forEach is not a function
    at /home/gymdo/STGdev/lvvn/node_modules/extract-text-webpack-plugin/dist/loader.js:145:16

I've spent 10 hours trying to fix it ... searching and trying things .... This error happens when my webpack.mix.js is the original installation.

Looks the same as this ... https://www.bountysource.com/issues/92161278-unexpectedly-fails-with-css-loader-v4-0-0

OK, crickets ..... I don't think Spark is really usable for us .......

Is there anyway I can trade my unused Spark License in for a Nova License ???

OK, crickets ..... I don't think Spark is really usable for us .......

Is there anyway I can trade my unused Spark License in for a Nova License ???

Sure, ensure you have already been updated to Win10 version 2004 (April 2020), then go to the Microsoft Store and get Linux Ubuntu 20 and Microsoft Terminal (preview), both free. Follow the directions and you will have a full Ubuntu (sans the GUI) with BASH shell.

You can access the Windows file system from within WSL; where C:\Users\username under Ubuntu is /mnt/c/Users/username

You can also access the Linux file sys from Windows Explorer with \wsl$\Ubuntu-20.04\home\username

I recommend using /home/username as your repo (dev) area. Using /mnt/c/Users/username works but is very slow comparatively.

I find WSL much easier to use than Homestead.

I'm using WSL2 with Ubuntu 20 on Win v2004 and it's working great. I started out using my dev area under /mnt/c/Users/username/ but everyting is 10x faster without the windows file system. I moved to /home/username/ Using Laravel 7 and vscode.

OK, anybody skipped Homestead to use Ubuntu 20 in WSL under Windows May release 2004? I've doing it now for a month with good success. We could start a support group somewhere?!?

---Jim in Florida

I would like to add vuetify to a new spark project. Is this a good? bad? idea?

Could someone point me to tutorial to use the latest vuetify with the latest spark or close to latest.

Thanks, Jim in Florida

I would like to add vuetify to a new spark project. Is this a good? bad? idea?

Could someone point me to tutorial to use the latest vuetify with the latest spark or close to latest.

Thanks, Jim in Florida

Yes, for whatever reason, I assumed that all stuff like vue init webpack-simple, etc had to run inside the box. I guess I need to start thinking outside the box....get it??.....never thot I'd really be able to say that!

OK, I;m following along in the Vue training video and trying to install and run this, and all seems to install OK but I'm not able to get chrome to connect to http://localhost:8080

I'm in Windows in Homestead. I do have chrome connected to Homestead.test and spark.test that I set up. When I try to clean up the npm install vulnerabilities, the npm run dev errors out with a missing webpack file.

Thanks, Jim in Florida

npm notice created a lockfile as package-lock.json. You should commit this file.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected]^1.2.7 (node_modules/chokidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for [email protected]: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})

added 810 packages from 579 contributors and audited 10095 packages in 153.755s

22 packages are looking for funding
  run `npm fund` for details

found 11 vulnerabilities (3 low, 4 moderate, 4 high)
  run `npm audit fix` to fix them, or `npm audit` for details
[email protected]:~/Laravel/hello-vue
$ npm run dev

> [email protected] dev /home/vagrant/Laravel/hello-vue
> cross-env NODE_ENV=development webpack-dev-server --open --hot

Project is running at http://localhost:8080/
webpack output is served from /dist/
404s will fallback to /index.html
Unable to open browser. If you are running in a headless environment, please do not use the open flag.
{ parser: "babylon" } is deprecated; we now treat it as { parser: "babel" }.

it's 7.4.5 should it be 7.2.5 ??

OK, so should I change composer.json

        "laravel/cashier": "^11.2",

to

        "laravel/cashier": "10.0",

and run > composer update ??

I seem to be at my last step of the install and get this problem. I did a > composer install

    1/2:        http://repo.packagist.org/p/provider-2020-04$dda39d483ecef141bc005276602492ebf76ece28f271d09f3ac9e0c27f497be4.json
    2/2:        http://repo.packagist.org/p/provider-latestf027bf03900e17ab40e7e0f3ced1a371d7005d2cfc5e3901e416501c8e6e1f0.json
    Finished: success: 2, skipped: 0, failure: 0, total: 2
Loading composer repositories with package information
Updating dependencies (including require-dev)
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Installation request for laravel/spark-aurelius ~9.0 -> satisfiable by laravel/spark-aurelius[v9.0.0, v9.0.1, v9.0.2, v9.0.3, v9.0.4, v9.0.5, v9.0.6, v9.0.7, v9.0.8, v9.0.9, 9.0.x-dev, v9.1.0, v9.1.1, v9.2.0, v9.2.1, v9.2.2].
    - Can only install one of: laravel/cashier[10.0.x-dev, v11.2.2].
    - Can only install one of: laravel/cashier[11.x-dev, 10.0.x-dev].
    - Can only install one of: laravel/cashier[v11.2.0, 10.0.x-dev].
    - Can only install one of: laravel/cashier[v11.2.1, 10.0.x-dev].
    - Can only install one of: laravel/cashier[v11.2.2, 10.0.x-dev].
    - Conclusion: install laravel/cashier 10.0.x-dev
    - Installation request for laravel/cashier ^11.2 -> satisfiable by laravel/cashier[11.x-dev, v11.2.0, v11.2.1, v11.2.2].

my composer.json is ----

{
    "name": "laravel/laravel",
    "type": "project",
    "description": "The Laravel Framework.",
    "keywords": [
        "framework",
        "laravel"
    ],
    "license": "MIT",
    "require": {
        "php": "^7.2.5",
        "fideloper/proxy": "^4.2",
        "fruitcake/laravel-cors": "^1.0",
        "guzzlehttp/guzzle": "^6.3",
        "laravel/cashier": "^11.2",
        "laravel/framework": "^7.0",
        "laravel/tinker": "^2.0",
        "laravel/ui": "^2.0",
        "laravel/spark-aurelius": "~9.0"
        },
    "require-dev": {
        "facade/ignition": "^2.0",
        "fzaninotto/faker": "^1.9.1",
        "mockery/mockery": "^1.3.1",
        "nunomaduro/collision": "^4.1",
        "phpunit/phpunit": "^8.5"
    },
    "config": {
        "optimize-autoloader": true,
        "preferred-install": "dist",
        "sort-packages": true
    },
    "extra": {
        "laravel": {
            "dont-discover": []
        }
    },
    "autoload": {
        "psr-4": {
            "App\": "app/"
        },
        "classmap": [
            "database/seeds",
            "database/factories"
        ]
    },
    "autoload-dev": {
        "psr-4": {
            "Tests\": "tests/"
        }
    },
    "minimum-stability": "dev",
    "prefer-stable": true,
    "repositories": [
        {
            "type": "composer",
            "url": "https://spark-satis.laravel.com"
        }
    ],
    "scripts": {
        "post-autoload-dump": [
            "Illuminate\Foundation\ComposerScripts::postAutoloadDump",
            "@php artisan package:discover --ansi"
        ],
        "post-root-package-install": [
            "@php -r \"file_exists('.env') || copy('.env.example', '.env');\""
        ],
        "post-create-project-cmd": [
            "@php artisan key:generate --ansi"
        ]
    }
}

My composer.lock file includes ---- But, has no spark entry ---

        {
            "name": "laravel/cashier",
            "version": "v11.2.2",
            "source": {
                "type": "git",
                "url": "https://github.com/laravel/cashier.git",
                "reference": "329f4e0bd93bef837e9291b2d09915009bda578f"
            },
            "dist": {
                "type": "zip",
                "url": "https://api.github.com/repos/laravel/cashier/zipball/329f4e0bd93bef837e9291b2d09915009bda578f",
                "reference": "329f4e0bd93bef837e9291b2d09915009bda578f",
                "shasum": ""
            },
            "require": {
                "dompdf/dompdf": "^0.8.0",
                "ext-json": "*",
                "illuminate/contracts": "^6.0|^7.0",
                "illuminate/database": "^6.0|^7.0",
                "illuminate/http": "^6.0|^7.0",
                "illuminate/log": "^6.0|^7.0",
                "illuminate/notifications": "^6.0|^7.0",
                "illuminate/routing": "^6.0|^7.0",
                "illuminate/support": "^6.0|^7.0",
                "illuminate/view": "^6.0|^7.0",
                "moneyphp/money": "^3.2",
                "nesbot/carbon": "^2.0",
                "php": "^7.2",
                "stripe/stripe-php": "^7.0",
                "symfony/http-kernel": "^4.3|^5.0",
                "symfony/intl": "^4.3|^5.0"
            },
            "require-dev": {
                "mockery/mockery": "^1.0",
                "orchestra/testbench": "^4.0|^5.0",
                "phpunit/phpunit": "^8.0|^9.0"
            },
            "suggest": {
                "ext-intl": "Allows for more locales besides the default \"en\" when formatting money values."
            },
            "type": "library",
            "extra": {
                "branch-alias": {
                    "dev-master": "11.x-dev"
                },
                "laravel": {
                    "providers": [
                        "Laravel\Cashier\CashierServiceProvider"
                    ]
                }
            },
            "autoload": {
                "psr-4": {
                    "Laravel\Cashier\": "src/"
                }
            },
            "notification-url": "https://packagist.org/downloads/",
            "license": [
                "MIT"
            ],
            "authors": [
                {
                    "name": "Taylor Otwell",
                    "email": "[email protected]"
                }
            ],
            "description": "Laravel Cashier provides an expressive, fluent interface to Stripe's subscription billing services.",
            "keywords": [
                "billing",
                "laravel",
                "stripe"
            ],
            "time": "2020-04-28T15:44:32+00:00"
        },

Thanks, Jim in Florida