72 package suggestions were added by new dependencies, use composer suggest to see details.
Generating optimized autoload files
Illuminate\Foundation\ComposerScripts::postAutoloadDump
#php artisan package:discover --ansi
Discovered Package: laravel/sail
Discovered Package: laravel/sanctum
Discovered Package: laravel/tinker
Discovered Package: nesbot/carbon
Discovered Package: nunomaduro/collision
Discovered Package: spatie/laravel-ignition
Package manifest generated successfully.
78 packages you are using are looking for funding.
Use the composer fund command to find out more!
#php artisan vendor:publish --tag=laravel-assets --ansi --force
No publishable resources for tag [laravel-assets].
Publishing complete.
#php artisan key:generate --ansi
Application key set successfully.
HP PC#DESKTOP-OE743IG MINGW64 /c/xampp/htdocs
$ ^C
HP PC#DESKTOP-OE743IG MINGW64 /c/xampp/htdocs
$ cd laravel8MOM
HP PC#DESKTOP-OE743IG MINGW64 /c/xampp/htdocs/laravel8MOM
$ composer require livewire/livewire
Using version ^2.10 for livewire/livewire
./composer.json has been updated
Running composer update livewire/livewire
Loading composer repositories with package information
Updating dependencies
Lock file operations: 1 install, 0 updates, 0 removals
Locking livewire/livewire (v2.10.6)
Writing lock file
Installing dependencies from lock file (including require-dev)
Package operations: 1 install, 0 updates, 0 removals
Installing livewire/livewire (v2.10.6): Extracting archive
Generating optimized autoload files
Illuminate\Foundation\ComposerScripts::postAutoloadDump
#php artisan package:discover --ansi
Discovered Package: laravel/sail
Discovered Package: laravel/sanctum
Discovered Package: laravel/tinker
Discovered Package: livewire/livewire
Discovered Package: nesbot/carbon
Discovered Package: nunomaduro/collision
Discovered Package: spatie/laravel-ignition
Package manifest generated successfully.
79 packages you are using are looking for funding.
Use the composer fund command to find out more!
#php artisan vendor:publish --tag=laravel-assets --ansi --force
No publishable resources for tag [laravel-assets].
Publishing complete.
Related
I created a fork from react-native-calendar. But it doesn't add all files when I try to install it with npm. for example in the calendar folder, there is not any JS and TS file. You can check my forked version here.
Forked Package:
Original Package:
✅ Solved:
The package needs to preinstall
Environment: Windows, Node 16.18.0, Corepack 0.14.1
I am following these instructions to install Yarn.
When I run corepack prepare yarn#3.2.4 or corepack prepare yarn#3.2.4 --activate
I get the following error:
Preparing yarn#3.2.4... Internal Error: ENOENT: no such file or directory, stat 'C:\Users\rashiditaba\AppData\Local\node\corepack\yarn\3.2.4' Error: ENOENT: no such file or directory, stat 'C:\Users\***\AppData\Local\node\corepack\yarn\3.2.4'
Hello I experienced the same problem. Corepack is an experimental tool to help with managing versions of your package managers. Due to its experimental status, Corepack currently needs to be explicitly enabled to have any effect.
Disable Corepack with the command:
corepack disable
You will now be able to install yarn via npm:
npm install -g yarn --force
To check the installed version of yarn use:
yarn -v
To upgrade the version use (stable version 3.2.4):
yarn set version stable
Now you can enable corepack again (if it fails keep it disabled):
corepack enable
Try the failed command:
corepack prepare yarn#3.2.4 --activate
I leave you the link with the description of the solution:
https://nodejs.org/dist/latest/docs/api/corepack.html
I hope it helps you
From the error your getting it seems like you have to wrong directory PATH to yarn. Find the directory where yarn is installed and update it's PATH in the environment variables.
I recently updated bower via npm i -g bower and it pulled latest version of 1.8.3.
Now running bower i immediately fails with:
module.js:538
throw err;
^
Error: Cannot find module 'q'
FYI: Workaround is explicitly install 1.8.2 via npm i -g bower#1.8.2
Not that this solves the exact problem, but if you look on the Bower package:
This package has been deprecated Author message:
...psst! Your project can stop working at any moment because its
dependencies can change. Prevent this by migrating to Yarn:
https://bower.io/blog/2017/how-to-migrate-away-from-bower/
They recommend you use a package called Yarn
I am trying to add the mapbox gl package to my Aurealia Typescript skeleton using jspm. I am using the following command.
jspm install npm:mapbox-gl
This is what I am getting.
Looking up npm:mapbox-gl
Updating registry cache...
Downloading npm:mapbox-gl#0.19.1
warn Error on processPackageConfig
Package.json dependency mapbox-gl-shaders set to github:mapbox/mapbox-gl-shaders#e4737bb136d718f9c5fe8d943380f05db6249b57, which is not a valid dependency format for npm.
It's advisable to publish jspm-style packages to GitHub or another registry so conventions are clear.
warn Error processing package config for npm:mapbox-gl.
err Error processing package config for npm:mapbox-gl.
warn Installation changes not saved.
I am using jspm 0.16.36.
When I try to install the package via npm install mapbox-gl it works normally. Any suggestions?
Considering you are using jspm, you might also want to try and reference it through the GitHub repo rather than through npm:
$ jspm install github:mapbox/mapbox-gl-js
It works for me with jspm v16.x and v0.21.0 of MapboxGL.
While attempting to build a custom version of jQuery without installing global dependencies, I ran into the following issue:
$ node --version
v0.10.4
$ npm --version
1.2.18
$ git clone git://github.com/jquery/jquery.git
$ cd jquery
$ git checkout `git describe --abbrev=0 --tags` # latest tag
$ npm install
$ npm install grunt-cli
# variant A
$ npm run-script grunt custom:-ajax # does nothing
# variant B
$ node_modules/.bin/grunt custom:-ajax
Running "custom:-ajax" (custom) task
Creating custom build...
Warning: Error: not found: grunt Use --force to continue.
Aborted due to warnings.
I haven't worked with Grunt or Node much before, so what am I missing here?
This is because of how the jQuery custom task spawns grunt. I've just sent a pull request which would fix this issue: https://github.com/jquery/jquery/pull/1255