The registration verify email is not working, I'm not getting any errors. The account is created but the email is not sent out. The email module in Admin is working fine, emails are getting sent out.

I can't find where the email is getting created and sent, there must be an event listener somewhere. I am unable to hunt it down.

Hello guys. I got the next error trying to run npm run dev

`$ npm run dev

@coreui/[email protected] dev /home/xxx/public_html/demo
npm run development

@coreui/[email protected] development /home/xxx/public_html/demo
cross-env NODE_ENV=development node_modules/webpack/bin/webpack.js --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js

node[31065]: pthread_create: Resource temporarily unavailable
10% building 1/1 modules 0 activenpm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! @coreui/[email protected] development: 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! Exit status 1
npm ERR!
npm ERR! Failed at the @coreui/[email protected] development 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/xxx/.npm/_logs/2020-03-05T07_32_12_246Z-debug.log
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! @coreui/[email protected] dev: npm run development
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the @coreui/[email protected] 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/xxx/.npm/_logs/2020-03-05T07_32_12_260Z-debug.log`

And here is the content of log:

0 info it worked if it ends with ok 1 verbose cli [ '/usr/local/bin/node', 1 verbose cli '/usr/local/bin/npm', 1 verbose cli 'run', 1 verbose cli 'development' ] 2 info using [email protected] 3 info using [email protected] 4 verbose run-script [ 'predevelopment', 'development', 'postdevelopment' ] 5 info lifecycle @coreui/[email protected]~predevelopment: @coreui/[email protected] 6 info lifecycle @coreui/[email protected]~development: @coreui/[email protected] 7 verbose lifecycle @coreui/[email protected]~development: unsafe-perm in lifecycle true 8 verbose lifecycle @coreui/[email protected]~development: PATH: /usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/home/xxx/public_html/demo/node_modules/.bin:/usr/local/li$ 9 verbose lifecycle @coreui/[email protected]~development: CWD: /home/xxx/public_html/demo 10 silly lifecycle @coreui/[email protected]~development: Args: [ '-c', 10 silly lifecycle 'cross-env NODE_ENV=development node_modules/webpack/bin/webpack.js --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js' ] 11 silly lifecycle @coreui/[email protected]~development: Returned: code: 1 signal: null 12 info lifecycle @coreui/[email protected]~development: Failed to exec development script 13 verbose stack Error: @coreui/[email protected] development:cross-env NODE_ENV=development node_modules/webpack/bin/webpack.js --progress --hide-modules --config=node_modules/laravel-mix/setup/webpac$
13 verbose stack Exit status 1
13 verbose stack at EventEmitter. (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:285:16)
13 verbose stack at EventEmitter.emit (events.js:180:13)
13 verbose stack at ChildProcess. (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
13 verbose stack at ChildProcess.emit (events.js:180:13)
13 verbose stack at maybeClose (internal/child_process.js:936:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:220:5)
14 verbose pkgid @coreui/[email protected]
15 verbose cwd /home/xxx/public_html/demo
16 verbose Linux 3.10.0-957.5.1.el7.x86_64
17 verbose argv "/usr/local/bin/node" "/usr/local/bin/npm" "run" "development"
18 verbose node v9.8.0
19 verbose npm v5.6.0
20 error code ELIFECYCLE
21 error errno 1
22 error @coreui/[email protected] development: cross-env NODE_ENV=development node_modules/webpack/bin/webpack.js --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js
22 error Exit status 1
23 error Failed at the @coreui/[email protected] development script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]

`

Not sure if this is a bug or something on my end. Is the Admin role supposed to be able to edit the menu? I get a 403, User does not have the right roles.

Here is the seeder from your code:

    $user = User::create([
        'name' => 'AJ',
        'email' => '[email protected]',
        'email_verified_at' => now(),
        'password' => 'taken out for security', // password
        'remember_token' => Str::random(10),
        'menuroles' => 'user,admin'
    ]);
    $user->assignRole('admin');

Sidebar menu does not collapse most of the time.
I noticed that there is a relation between drop down menus and sidebar menu, only one of them work properly at one moment.

• after install and run the project, the default widgets card-chart not show any tooltips.
  got this warning too:
  bar chart: "scales.[x/y]Axes.barPercentage" is deprecated. Please use "dataset.barPercentage" instead
• and the route /widgets as admin not found js/coreui-chartjs.js

Migrating: 2014_10_12_000000_create_users_table

Illuminate\Database\QueryException : SQLSTATE[42000]: Syntax error or access violation: 1071 Specified key was too long; max key length is 767 bytes (SQL: alter tableusersadd uniqueusers_email_unique(email))

On following the install directions to the letter for a default starter project, I'm getting lots of failed tests in PHPUnit. Some of these I've been able to resolve with a little elbow grease but it seems like maybe I'm either doing something wrong or the tests may be in need of updating. Can anyone confirm if the test suite currently has quite a few failures for the starter/example project or if it's just me?

ERRORS! Tests: 189, Assertions: 315, Errors: 32, Failures: 39.

Thanks!

After the startup of the project in the console you get an error, saying that in the public/js folder popper.js.map hasn´t been found, i went through the webpack.mix.js file and i dont´t know if intentionally or not but you guys did not include it, so i thought i file the issue. Take a look and you will tell me, thanks for this awesome pack of cool gadgets and stuff, laravel is alredy a great tool but with these you just make it that much more awesome! Take care!

Its my fresh installation and happens this after login with the default admin@admin user.

I got an error while installing coreui on the subdomain,

@coreui/[email protected] development /home/****
cross-env NODE_ENV=development node_modules/webpack/bin/webpack.js --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js

/home/*****/node_modules/cross-env/src/index.js:23
)
^
SyntaxError: Unexpected token )
at Object.exports.runInThisContext (vm.js:76:16)
at Module._compile (module.js:542:28)
at Object.Module._extensions..js (module.js:579:10)
at Module.load (module.js:487:32)
at tryModuleLoad (module.js:446:12)
at Function.Module._load (module.js:438:3)
at Module.require (module.js:497:17)
at require (internal/module.js:20:19)
at Object. (/home/****/node_modules/cross-env/src/bin/cross-env.js:3:18)
at Module._compile (module.js:570:32)

npm ERR! Linux 2.6.32-042stab145.3
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "run" "development"
npm ERR! node v6.9.2
npm ERR! npm v3.10.9
npm ERR! code ELIFECYCLE
npm ERR! @coreui/[email protected] development: 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! Exit status 1
npm ERR!
npm ERR! Failed at the @coreui/[email protected] development script '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! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the @coreui/coreui-free-laravel-admin-template package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! 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! You can get information on how to open an issue for this project with:
npm ERR! npm bugs @coreui/coreui-free-laravel-admin-template
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls @coreui/coreui-free-laravel-admin-template
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR! /home/****/npm-debug.log

Hello,

We have a strange problem creating BREADs. We are able to create them by associating them with the right table. Once the form it is created, we can see it with the show option, but if we try access it through resources to view the table or to add records, the program crashes and takes us to the login page of the dashboard, without any warning or undertandable error messe.

The example provided is working correctly, also we have seen that the fields listed in it, are less than the fields in the database.

What could be the problem?

Regards,

Using the code below, I was able to add a new user with new role in to the database. But the problem is the Menu is not visible or added to the sidebar for the users with additional role. everything is working for the default user and admin roles.

What am I missing here

        $user = User::create([
            'name' => 'APP Admin',
            'email' => '[email protected]',
            'email_verified_at' => now(),
            'password' => '$2y$10$92IXUNpkjO0rOQ5byMi.Ye4oKoEa3Ro9llC/.og/at2.uheWG/igi', // password
            'remember_token' => Str::random(10),
            'menuroles' => 'user,siteadmin,tutor'
        ]);
        $user->assignRole('user'); 
        $user->assignRole('siteadmin');
        $user->assignRole('tutor'); 

Edit:
I have looked into the MenusTableSeeder.php to adjust the menuroles string but the menu items are not visible if user string is not added, user is the lowest roles

There is also an instance where
$this->insertLink('admin,siteadmin,tutor', 'Add a Class', '/classroom/add');

I seem to be running into an issue in the installation process.

Problem 1
- spatie/laravel-medialibrary is locked to version 8.7.2 and an update of this package was not requested.
- spatie/laravel-medialibrary 8.7.2 requires php ^7.4 -> your php version (7.3.31) does not satisfy that requirement.

As you can see i am running PHP 7.3.31, When i try to run PHP 7.4 I receive a similar log output for different dependencies specifying that they require PHP 7.3.

What is the best way for me to resolve this as it seems the dependencies require different versions of PHP to function?

The links keep going to localhost, which doesn't work, but 127.0.0.1:8000 does. How do I make that change with your template?

Example: http://localhost/login is what I get when I click on the Login button on the left side.

After i did "php artisan ui:auth". This error shows up when i access /login.

If you install this template then you can get this errors

Unknown named parameter $note
...
Unknown named parameter $user

From official documentation:

By default, Route::resource will create the route parameters for your resource routes based on the "singularized" version of the resource name.

So for routes that generates using resource there should be methods in controllers with appropriate param names. But in current controllers this param names like $id and not like singularized version. So we should change routes or controller param names. the easy way to fix route files like this:

Route::resource('notes', 'NotesController')->parameters([ 'notes' => 'id']);
...
Route::resource('users', 'UsersController')->except( ['create', 'store'] )->parameters([ 'users' => 'id']);

and etc.

I have error

> npm ERR! code 1
> npm ERR! path /var/www/coreuicuba
> npm ERR! command failed
> npm ERR! command sh -c 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! A complete log of this run can be found in:
> npm ERR!     /home/laradock/.npm/_logs/2020-12-22T10_50_41_923Z-debug.log
> npm ERR! code 1
> npm ERR! path /var/www/coreui
> npm ERR! command failed
> npm ERR! command sh -c npm run development
> 
> npm ERR! A complete log of this run can be found in:
> npm ERR!     /home/laradock/.npm/_logs/2020-12-22T10_50_41_970Z-debug.log

I have done run npm audit fix command and I have an error

> braces  <2.3.1
> Regular Expression Denial of Service - https://npmjs.com/advisories/786
> fix available via `npm audit fix`
> node_modules/sync-glob/node_modules/braces
>   micromatch  0.2.0 - 2.3.11
>   Depends on vulnerable versions of braces
>   node_modules/sync-glob/node_modules/micromatch
>     anymatch  1.2.0 - 1.3.2
>     Depends on vulnerable versions of micromatch
>     node_modules/sync-glob/node_modules/anymatch
>       chokidar  1.3.0 - 1.7.0
>       Depends on vulnerable versions of anymatch
>       node_modules/sync-glob/node_modules/chokidar
> 
> yargs-parser  <=13.1.1 || 14.0.0 - 15.0.0 || 16.0.0 - 18.1.1
> Prototype Pollution - https://npmjs.com/advisories/1500
> No fix available
> node_modules/sync-glob/node_modules/yargs-parser
>   yargs  4.0.0-alpha1 - 12.0.5 || 14.1.0 || 15.0.0 - 15.2.0
>   Depends on vulnerable versions of yargs-parser
>   node_modules/sync-glob/node_modules/yargs
>     sync-glob  *
>     Depends on vulnerable versions of yargs
>     node_modules/sync-glob
> 
> 7 low severity vulnerabilities
> 

I have done follow in laravel-mix/laravel-mix#2389 (comment) . but still failed.
I don't know how to fix it. there may be a suggestion to improve it.

Hello there,
I have an issue where whenever I try to install the template I get my page like this picture

So I'm trying to install it with laravel..
I tried to follow the instruction in coreui doc and I tried to follow a tutorial on youtube made by laravel daily but both give the same result

runing php artisan migrate:refresh --seed
I get
SQLSTATE[22001]: String data, right truncated: 1406 Data too long for column 'description' at row 1 (SQL: insert into example (name, description, status_id) values (Velit architecto voluptates quam et., Qui voluptatibus possimus tenetur et sapiente esse distinctio. Alias est est ipsam dicta praesentium. Ducimus perspiciatis aut enim nobis suscipit enim ducimus. Consequatur ipsa sit nulla exercitationem reiciendis qui placeat. Voluptatum consequatur molestias ex voluptatem., 4))

I've fixed it changing
\database\seeds\ExampleSeeder.php
'description' => $faker->paragraph(3,true),
to
'description' => $faker->paragraph(2,true),

Thanks!

how to add custom validation in column

Can we upgrade Laravel to the newest version?

The required version of php may need to be updated in the composer.json. my php version is php 7.3, can I downgrade the spatie/laravel-medialibrary?

CoreUI is nothing without our community, that’s why I’m thrilled to announce that we created one place where you can talk and get help regarding all CoreUI Products.

When asking the general "how to" questions please post your question here - https://community.coreui.io/c/support/coreui-laravel-admin-template/19

Please use GitHub only when reporting a bug, all issues with the general "how to" questions will be automatically closed.

When I came in to work on Tuesday, July 6th I noticed a new error:

Uncaught TypeError: Cannot set property 'Constructor' of undefined.

It appears to be linked to this CDN:

https://unpkg.com/@coreui/coreui/dist/js/coreui.bundle.min.js

When I comment it out, the error goes away, but the sidebar has issues either way:

• dropdown doesn't work
• collapse doesn't work

How to add sidebar aside on right panel?

Running composer updates results in unresolvable dependencies.

I tried to install coreui laravel admin template.
But get an error while run "npm install".
Here is the error

I tried to uninstall and reinstall, got the same error.

You told me that a new release was coming out by the end of the month, and it is now the 30th May 30, 2021. And I don’t see a, new relics, or an update here on GitHub; when will it be ready and how do I get It.?

Hey,
I just tried to install CoreUI but the migration to the database failed. Does anyone has an idea what is wrong?

Migrating: 2020_01_08_184500_create_media_table

   Illuminate\Database\QueryException

  SQLSTATE[42000]: Syntax error or access violation: 1064 You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near 'json not null, `custom_properties` json not null, `responsive_images` json not n' at line 1 (SQL: create table `media` (`id` bigint unsigned not null auto_increment primary key, `model_type` varchar(191) not null, `model_id` bigint unsigned not null, `collection_name` varchar(191) not null, `name` varchar(191) not null, `file_name` varchar(191) not null, `mime_type` varchar(191) null, `disk` varchar(191) not null, `size` bigint unsigned not null, `manipulations` json not null, `custom_properties` json not null, `responsive_images` json not null, `order_column` int unsigned null, `created_at` timestamp null, `updated_at` timestamp null) default character set utf8mb4 collate 'utf8mb4_unicode_ci')

  at C:\Users\Joschua\Documents\GitHub\horizon-support-web\vendor\laravel\framework\src\Illuminate\Database\Connection.php:670
    666|         // If an exception occurs when attempting to run a query, we'll format the error
    667|         // message to include the bindings with SQL, which will make this exception a
    668|         // lot more helpful to the developer instead of just the database's errors.
    669|         catch (Exception $e) {
  > 670|             throw new QueryException(
    671|                 $query, $this->prepareBindings($bindings), $e
    672|             );
    673|         }
    674|

  1   C:\Users\Joschua\Documents\GitHub\horizon-support-web\vendor\laravel\framework\src\Illuminate\Database\Connection.php:458
      PDOException::("SQLSTATE[42000]: Syntax error or access violation: 1064 You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near 'json not null, `custom_properties` json not null, `responsive_images` json not n' at line 1")

  2   C:\Users\Joschua\Documents\GitHub\horizon-support-web\vendor\laravel\framework\src\Illuminate\Database\Connection.php:458
      PDO::prepare()

When the sidebar is collapsed, the perfect scrollbar is removed completely (which shouldn't happen in the first place imo), but when you expand the sidebar back to the original position, the perfect scrollbar is never restored.

https://coreui.io/docs/components/bootstrap/modal/#modifying-modal-content

show.coreui.modal not work

vendor/spatie/laravel-medialibrary/src/MediaCollections/Models/Media.php:182

Error on this line

    return $conversions->map(fn (Conversion $conversion) => $conversion->getName())->toArray();

How can i activate vue components? i tried but i can´t do it

Python Command Failed.

I could not install . Please the attached screen shot.

Hi everyone!

Trying to use the forgot password feature I noticed that both views (email.blade.php and reset.blade.php) are still using the Laravel default files, so they extend the app.blade.php view, that don't work in coreui. Is there a plan to migrate both views to coreui theme? Or how can I integrate both views to the main theme?

Role::all()->pluck('name')->toArray();

Facade\Ignition\Exceptions\ViewException
Undefined variable: langs (View: ___\resources\views\dashboard\editmenu\show.blade.php) when accessing http://localhost:8000/menu/element/show?id=1

I get the following error when running the migration:

Illuminate\Database\QueryException : SQLSTATE[42000]: Syntax error or access violation: 1064 You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near 'json not null, custom_properties json not null, responsive_images json not n' at line 1 (SQL: create table media (id bigint unsigned not null auto_increment primary key, model_type varchar(191) not null, model_id bigint unsigned not null, collection_name varchar(191) not null, name varchar(191) not null, file_name varchar(191) not null, mime_type varchar(191) null, disk varchar(191) not null, size bigint unsigned not null, manipulations json not null, custom_properties json not null, responsive_images json not null, order_column int unsigned null, created_at timestamp null, updated_at timestamp null) default character set utf8mb4 collate 'utf8mb4_unicode_ci')

As the topic mentioned, I would like to use the Laravel 6 LTS version as my project requirement. Is it possible with pro version?

npm install drops with error
Log file last lines:
24076 silly extract [email protected] extracted to C:\laragon\www\coreui\node_modules.staging\core-js-eabcedc4 (70705ms)
24077 silly extract @coreui/[email protected] extracted to C:\laragon\www\coreui\node_modules.staging@coreui\coreui-8af33aaf (47896ms)
24078 silly extract [email protected] extracted to C:\laragon\www\coreui\node_modules.staging\rxjs-4e93b4be (272403ms)
24079 timing npm Completed in 426358ms
24080 error cb() never called!

npm --v
6.14.8
Laravel Framework 8.6.0
Windows 10

I have two roles for my account: Employee and Admin.

I can't see the menu elements that have only the role Employee. If I remove all roles from my account except Employee, I can see the menu. Why is that?

using "@coreui/coreui": "^3.0.0".
Checking the chrome console log. Can see user messages below come up always in coreui.bundle.min.js:6

<div class="tooltip fade" role="tooltip" id="tooltip109586" style="margin: 0px;"><div class="tooltip-arrow" style=""></div><div class="tooltip-inner">Click to add permission</div></div>

[Composer\Repository\InvalidRepositoryException] Invalid repository data in /Users/xxxx/PhpstormProjects/coreui/vendor/composer/installed.json, packages could not be loaded: [Seld\JsonLint\Parsin gException] "/Users/xxxx/PhpstormProjects/coreui/vendor/composer/installed.json" does not contain valid JSON Parse error on line 2: [ {<<<<<<< HEAD -----^ Expected one of: 'STRING', '}'

I just cloned this project today. I haven't changed anything that would affect this. When I try to logout, it just refreshes the page.

Loads of issues

[a] Conflicting PHP versions, some of the addons what one extension and others another
[b] Uses many deprecated classes
[b] NPM won't compile. These are the errors I got:
npm WARN old lockfile
npm WARN old lockfile The package-lock.json file was created with an old version of npm,
npm WARN old lockfile so supplemental metadata must be fetched from the registry.
npm WARN old lockfile
npm WARN old lockfile This is a one-time fix-up, please be patient...
npm WARN old lockfile
npm WARN deprecated [email protected]: request-promise-native has been deprecated because it extends the now deprecated request package, see request/request#3142
npm WARN deprecated [email protected]: Please see https://github.com/lydell/urix#deprecated
npm WARN deprecated [email protected]: this library is no longer supported
npm WARN deprecated [email protected]: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (debug-js/debug#797)
npm WARN deprecated [email protected]: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (debug-js/debug#797)
npm WARN deprecated [email protected]: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (debug-js/debug#797)
npm WARN deprecated [email protected]: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (debug-js/debug#797)
npm WARN deprecated [email protected]: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (debug-js/debug#797)
npm WARN deprecated [email protected]: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (debug-js/debug#797)
npm WARN deprecated [email protected]: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (debug-js/debug#797)
npm WARN deprecated [email protected]: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (debug-js/debug#797)
npm WARN deprecated [email protected]: https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated [email protected]: Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies.
npm WARN deprecated [email protected]: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (debug-js/debug#797)
npm WARN deprecated [email protected]: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (debug-js/debug#797)
npm WARN deprecated [email protected]: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (debug-js/debug#797)
npm WARN deprecated [email protected]: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (debug-js/debug#797)
npm WARN deprecated [email protected]: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (debug-js/debug#797)
npm WARN deprecated [email protected]: Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies.
npm WARN deprecated [email protected]: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
npm WARN deprecated [email protected]: babel-eslint is now @babel/eslint-parser. This package will no longer receive updates.
npm WARN deprecated [email protected]: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details.
npm WARN deprecated [email protected]: request has been deprecated, see request/request#3142
npm WARN deprecated [email protected]: CoffeeScript on NPM has moved to "coffeescript" (no hyphen)
npm WARN deprecated [email protected]: Critical security vulnerability fixed in v0.21.1. For more information, see axios/axios#3410
npm WARN deprecated [email protected]: This version of tar is no longer supported, and will not receive security updates. Please upgrade asap.
npm WARN deprecated [email protected]: core-js@<3.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Please, upgrade your dependencies to the actual version of core-js.
npm ERR! code 1
npm ERR! path l:\laragon\www\core\node_modules\node-sass
npm ERR! command failed
npm ERR! command C:\WINDOWS\system32\cmd.exe /d /s /c node scripts/build.js
npm ERR! Building: C:\Program Files\nodejs\node.exe l:\laragon\www\core\node_modules\node-gyp\bin\node-gyp.js rebuild --verbose --libsass_ext= --libsass_cflags= --libsass_ldflags= --libsass_library=
npm ERR! gyp info it worked if it ends with ok
npm ERR! gyp verb cli [
npm ERR! gyp verb cli 'C:\Program Files\nodejs\node.exe',
npm ERR! gyp verb cli 'l:\laragon\www\core\node_modules\node-gyp\bin\node-gyp.js',
npm ERR! gyp verb cli 'rebuild',
npm ERR! gyp verb cli '--verbose',
npm ERR! gyp verb cli '--libsass_ext=',
npm ERR! gyp verb cli '--libsass_cflags=',
npm ERR! gyp verb cli '--libsass_ldflags=',
npm ERR! gyp verb cli '--libsass_library='
npm ERR! gyp verb cli ]
npm ERR! gyp info using [email protected]
npm ERR! gyp info using [email protected] | win32 | x64
npm ERR! gyp verb command rebuild []
npm ERR! gyp verb command clean []
npm ERR! gyp verb clean removing "build" directory
npm ERR! gyp verb command configure []
npm ERR! gyp verb check python checking for Python executable "python2" in the PATH
npm ERR! gyp verb which failed Error: not found: python2
npm ERR! gyp verb which failed at getNotFoundError (l:\laragon\www\core\node_modules\which\which.js:13:12)
npm ERR! gyp verb which failed at F (l:\laragon\www\core\node_modules\which\which.js:68:19)
npm ERR! gyp verb which failed at E (l:\laragon\www\core\node_modules\which\which.js:80:29)
npm ERR! gyp verb which failed at l:\laragon\www\core\node_modules\which\which.js:89:16
npm ERR! gyp verb which failed at l:\laragon\www\core\node_modules\isexe\index.js:42:5
npm ERR! gyp verb which failed at l:\laragon\www\core\node_modules\isexe\windows.js:36:5
npm ERR! gyp verb which failed at FSReqCallback.oncomplete (node:fs:193:21)
npm ERR! gyp verb which failed python2 Error: not found: python2
npm ERR! gyp verb which failed at getNotFoundError (l:\laragon\www\core\node_modules\which\which.js:13:12)
npm ERR! gyp verb which failed at F (l:\laragon\www\core\node_modules\which\which.js:68:19)
npm ERR! gyp verb which failed at E (l:\laragon\www\core\node_modules\which\which.js:80:29)
npm ERR! gyp verb which failed at l:\laragon\www\core\node_modules\which\which.js:89:16
npm ERR! gyp verb which failed at l:\laragon\www\core\node_modules\isexe\index.js:42:5
npm ERR! gyp verb which failed at l:\laragon\www\core\node_modules\isexe\windows.js:36:5
npm ERR! gyp verb which failed at FSReqCallback.oncomplete (node:fs:193:21) {
npm ERR! gyp verb which failed code: 'ENOENT'
npm ERR! gyp verb which failed }
npm ERR! gyp verb check python checking for Python executable "python" in the PATH
npm ERR! gyp verb which succeeded python C:\Python39\python.EXE
npm ERR! gyp ERR! configure error
npm ERR! gyp ERR! stack Error: Command failed: C:\Python39\python.EXE -c import sys; print "%s.%s.%s" % sys.version_info[:3];
npm ERR! gyp ERR! stack File "", line 1
npm ERR! gyp ERR! stack import sys; print "%s.%s.%s" % sys.version_info[:3];
npm ERR! gyp ERR! stack ^
npm ERR! gyp ERR! stack SyntaxError: invalid syntax
npm ERR! gyp ERR! stack
npm ERR! gyp ERR! stack at ChildProcess.exithandler (node:child_process:326:12)
npm ERR! gyp ERR! stack at ChildProcess.emit (node:events:369:20)
npm ERR! gyp ERR! stack at maybeClose (node:internal/child_process:1067:16)
npm ERR! gyp ERR! stack at Process.ChildProcess._handle.onexit (node:internal/child_process:301:5)
npm ERR! gyp ERR! System Windows_NT 10.0.19042
npm ERR! gyp ERR! command "C:\Program Files\nodejs\node.exe" "l:\laragon\www\core\node_modules\node-gyp\bin\node-gyp.js" "rebuild" "--verbose" "--libsass_ext=" "--libsass_cflags=" "--libsass_ldflags=" "--libsass_library="
npm ERR! gyp ERR! cwd l:\laragon\www\core\node_modules\node-sass
npm ERR! gyp ERR! node -v v15.12.0
npm ERR! gyp ERR! node-gyp -v v3.8.0
npm ERR! gyp ERR! not ok
npm ERR! Build failed with error code: 1

npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\Kingdel\AppData\Local\npm-cache_logs\2021-09-11T17_11_22_080Z-debug.log

Hello,
I'm having this issue:
SQLSTATE[42S01]: Base table or view already exists: 1050 Table 'permissions' already exists (SQL: create table permissions (id bigint unsigned not null auto_increment primary key, name varchar(255) not null, guard_name varchar(255) not null, created_at timestamp null, updated_at timestamp null) default character set utf8mb4 collate 'utf8mb4_unicode_ci')

Server version: 10.6.4-MariaDB MariaDB Server

Can you help to resolve this?

Thanks in advance.

Just tried a clean installation and get this:

Deprecation Notice: Class Tests\Unit\CoreUITest located in ./tests/Unit/@aCoreUITest.php does not comply with psr-4 autoloading standard. It will not autoload anymore in Composer v2.0. in phar:///usr/local/bin/composer/src/Composer/Autoload/ClassMapGenerator.php:201

the same code , migrate to aliycloud , then setup , npm run dev , go wrong

thanks help~

I have installed the fresh clone from this repo, but when i toggle screen to smartphone size, it come out like this, please tell me what i need to do?