Laravel Upgrading from Laravel 10 to Laravel 11

 The detailed upgrade document is available on the official Laravel document.

Also, read the Laravel 11 release notes. It will help us to upgrade our application.

1. PHP Version

Our first step is to upgrade your PHP version. Laravel 11 requires PHP 8.2.0 or greater.

2. Update Composer Dependencies

Now open our composer.json and update the following dependencies

• php to^8.2
• laravel/framework to ^11.0
• Remove the guzzlehttp/guzzle package. Because it is already included in laravel/framework
• nunomaduro/collision to ^8.1

I have updated some require-dev packages to match the Laravel 11 composer.json

diff --git a/composer.json b/composer.json
index 546a826..22a7942 100644
--- a/composer.json
+++ b/composer.json
@@ -5,25 +5,24 @@
     "keywords": ["framework", "laravel", "boilerplate", "admin panel"],
     "license": "MIT",
     "require": {
-        "php": "^8.1",
+        "php": "^8.2",
         "balajidharma/laravel-admin-core": "^1.0",
-        "guzzlehttp/guzzle": "^7.2",
-        "laravel/framework": "^10.0",
-        "laravel/sanctum": "^3.2",
-        "laravel/tinker": "^2.8",
+        "laravel/framework": "^11.0",
+        "laravel/tinker": "^2.9",
         "spatie/laravel-permission": "^5.5"
     },
     "require-dev": {
         "barryvdh/laravel-debugbar": "^3.7",
-        "fakerphp/faker": "^1.9.1",
+        "fakerphp/faker": "^1.23",
         "laravel/breeze": "^1.7",
         "laravel/dusk": "^7.1",
-        "laravel/pint": "^1.0",
-        "laravel/sail": "^1.18",
-        "mockery/mockery": "^1.4.4",
-        "nunomaduro/collision": "^7.0",
-        "phpunit/phpunit": "^10.0",
-        "spatie/laravel-ignition": "^2.0"
+        "laravel/pint": "^1.13",
+        "laravel/sail": "^1.26",
+        "mockery/mockery": "^1.6",
+        "nunomaduro/collision": "^8.1",
+        "phpunit/phpunit": "^10.5",
+        "spatie/laravel-ignition": "^2.4"
     },
     "autoload": {
         "psr-4": {

Also, update the below package if you have installed

• laravel/cashier-stripe to ^15.0
• laravel/passport to ^12.0
• laravel/sanctum to ^4.0
• laravel/spark-stripe to ^5.0
• laravel/telescope to ^5.0

3. Run composer update

We have updated all the dependencies on composer.json. Now is the time to run the composer update

./vendor/bin/sail composer update

I am getting the below error due to the laravel/breeze not supporting Laravel 11.

So, we need to find the latest version of laravel/breeze and add it to the composer.json file

• laravel/breeze to ^2.0

Now getting the same error forlaravel/dusk

so update Dusk to the latest version

• laravel/dusk to ^8.0

Again we getting errors, this time on our admin panel supporting packages

So, I am going to include Laravel 11 on both Laravel Menu and Laravel Category packages.

"illuminate/support": "^8.71|^9.0|^10.0|^11.0"

Again, this error is due to the spatie/laravel-permission. I am included spatie/laravel-permission in the application and admin code package.

So, going to remove spatie/laravel-permission and update the latest version of the admin code package.

finally, the composer update worked.

4. Check Laravel Version

To check the Laravel version, run the below command

./vendor/bin/sail artisan -v

//or

./vendor/bin/sail artisan --version

//If you not using sail
php artisan --version

Now our Admin Panel is using the Laravel 11.

5. Updating Sanctum

Now open the application in the browser. It throws the Fatal Error.

We are currently not using the Laravel Sanctum on the Admin Panel. So, I am going to remove the HasApiTokens from the user model.

Laravel 11 no longer supports Laravel Sanctum 3.x. Therefore, you should update your application’s Laravel Sanctum dependency to ^4.0 in your composer.json file.

If you're using Sanctum follow the steps mentioned in the upgrade document.

Now the admin panel is loading without errors

6. Remove Config Files

Taylor has introduced a slimmer config version. So, in Laravel 11 below the config is missing

• config/broadcasting.php
• config/cors.php
• config/hashing.php
• config/sanctum.php
• config/view.php

We can publish them manually, with this command

php artisan config:publish

OR

php artisan config:publish --all

So, we deleted the below config files similar to Laravel 11

        deleted:    config/broadcasting.php
        deleted:    config/cors.php
        deleted:    config/hashing.php
        deleted:    config/sanctum.php
        deleted:    config/view.php

7. Update package.json

Laravel 11 is using the Vite version 5. So, we are going to update the Vite version. Also, we going to add the type to the module on package.json.

Find below the updated package.json file.

diff --git a/package.json b/package.json
index 2effbfc..30feaba 100644
--- a/package.json
+++ b/package.json
@@ -1,20 +1,17 @@
 {
     "private": true,
+    "type": "module",
     "scripts": {
         "dev": "vite",
         "build": "vite build"
     },
     "devDependencies": {
         "@tailwindcss/forms": "^0.5.2",
-        "alpinejs": "^3.4.2",
         "autoprefixer": "^10.4.2",
-        "axios": "^1.1.2",
-        "laravel-vite-plugin": "^0.8.0",
-        "lodash": "^4.17.19",
-        "postcss": "^8.4.6",
-        "postcss-import": "^14.0.1",
+        "axios": "^1.6.4",
+        "laravel-vite-plugin": "^1.0",
         "tailwindcss": "^3.2.4",
-        "vite": "^4.0.0"
+        "vite": "^5.0"
     },
     "dependencies": {
         "daisyui": "^3.0.0",

We have removed alpinejs, lodash as per Laravel 11 package.json. We need to remove the alpinejs, lodash includes in resources/js/app.js and resources/js/bootstrap.js. After the removal, our app.js and bootstrap.js will have below-slim code.

resources/js/app.js

import './bootstrap';

resources/js/bootstrap.js

import axios from 'axios';
window.axios = axios;

window.axios.defaults.headers.common['X-Requested-With'] = 'XMLHttpRequest';

Now run the npm update after the npm update run the npm run dev

The fix the below error we need to update the postcss.config.js Because we updated the type as a module.

Add export default on postcss.config.js

export default {
    plugins: {
        tailwindcss: {},
        autoprefixer: {},
    },
};

Now our Laravel Admin Panel is upgraded with Laravel 11.

Thank you for reading.

Source : Balaji Dharma (Medium)

Read More

Upgrading an open source project to Laravel 11 with Shift

submitted by /u/mccreaja
[link] [comments]

Read More

Releasing a Filament JSON viewer/editor plugin [feedback is welcome]

Hi everyone!

Here's the link to the repo:


https://github.com/valentin-morice/filament-json-column

I was currently working on a project using Filament, and required a column to view and edit JSON data. I've found two plugins, jsoneditor and Pretty JSON, that would let me do either but not both at the same time, so I combined them.

If you'd feel like trying it, or have a look at the code, please do so. It's only my second package so I'd love to have some feedback. There's no testing since the plugin is mostly Alpine. Would you recommend doing some front-end testing using Dusk?

The future things I'm planning to work on:
- Blocking tab switching to viewer when JSON is invalid
- Moving from CDNs to npm
- Adding support for hints and other Filament methods submitted by /u/andre_ange_marcel
[link] [comments]

Read More

pandas/pyarrow ArrowTypeError: Unable to merge: Field on handcrafted partitioned parquet

I read the parquet file directly
pd.read_parquet(r'C:\Datasets\cn_data\dm\qmt\wqa_mfeatures\30m\year=2020\month=11\data.parquet')



No error will be reported.


But when I read the directory:
pd.read_parquet(r'C:\Datasets\cn_data\dm\qmt\wqa_mfeatures\30m\year=2020')



An error will be reported
ArrowTypeError: Unable to merge: Field month has incompatible types: int32 vs dictionary



This is because I handcrafted this partitioned path.
It is important that I have to hand craft the partitioned path.
I have 5000 item need transform and write to df.to_parquet(path, partition_cols=['year', 'month']) , and yes it would not overwrite existing files.



* But if I only need rerun 300 item, it would preduce new files, I can't delete the data produce by last run.

* With time goes, I need rerun transform function on new dates(year,month), I need new data overwrite old data.






I just want to keep pd.read_parquet function working with handcraft paths, this can reduce many works on reimplement a similar stuff and refactor pd.read_parquet in many projects.

Read More

autocommit when using Spring BatchSqlUpdate

We have been using spring with MSSQL jdbc driver for a while. It's an older project where we have an applicatonContext.xml file that defines a datasource transaction manager and each method uses a proxy.


If we switch to using Spring's BatchSqlUpdate do we need to somehow disable autocommit for this call to gain the full benefit? I read lots of posts about this but they all give examples with you are building your own queries and using your connection directly like this and many more: does my batch really execute as expected if autocommit is set to true?


But I can't find anyone talking about when doing it the "spring way". The connection will default to autocommit=true and that's good for all of our other methods. But now we have just a couple of batch ones and I don't see a method to set autocommit to false for a specific method/class.


I'll give more details, but does anyone know if we should disable autocommit for this (like it sounds from other posts) and if so how?


The details are we have this in the applicationContext.xml:









PROPAGATION_SUPPORTS
PROPAGATION_SUPPORTS
PROPAGATION_SUPPORTS
PROPAGATION_REQUIRED






and the datasource comes from wildfly standalone.xml. This all has been working great. Now we are working on using batch mode. Our sql update methods are like this (somewhat simplified)
protected class UpdateUserUpdate extends SqlUpdate {
public UpdateUserUpdate(DataSource ds) {
setDataSource(ds);
setSql("update whatever.. set value = ?")
declareParameter(new SqlParameter(Types.VARCHAR));
compile();
}
public int myupdate(String s) {
Object[] params = new Object[] { s };
return update(params);
}
}



And if we simply change the parent class to BatchSqlUpdate, it does work fine:
protected class UpdateUserUpdateBatch extends BatchSqlUpdate {
...copy as before but now add...
setBatchSize(1000);
}



And we do see some improvement. But would we see more if we can somehow disable the autocommit or is that even possible?


Or would it be faster to just create a method, feed it our array of entries, get a new connection from the datasource, and use PreparedStatement, like:
con = dataSource.getConnection();
con.setAutoCommit(false);
PreparedStatement pstmt = con.prepareStatement(sql);
do my add batch/executebatch in a 1000 loop...
pstmt.executeBatch();
con.commit();
con.setAutoCommit(false);



That is not the spring way but is it faster because I turned of autocommit or can you turn it of on BatchSqlUpdate?


Thank you!

Read More

zsh: bad CPU type in executable: node

I have installed nvm using brew. After that, I installed node version of 16 through nvm and check the current version using node -v to see whether the node is working properly. However, when I install version 14 or any other previous versions and runs node -v, it gives this "zsh: bad CPU type in executable: node" message and I have no idea what to do about this, though, installing node v17 and running node -v works as expected. Below are the snippet of the said commands.

Read More

Weekly /r/Laravel Help Thread

Ask your Laravel help questions here. To improve your chances of getting an answer from the community, here are some tips:

* What steps have you taken so far?
* What have you tried from the documentation?
* Did you provide any error messages you are getting?
* Are you able to provide instructions to replicate the issue?

* Did you provide a code example?

* Please don't post a screenshot of your code. Use the code block in the Reddit text editor and ensure it's formatted correctly.






For more immediate support, you can ask in the official Laravel Discord.

Thanks and welcome to the /r/Laravel community! submitted by /u/AutoModerator
[link] [comments]

Read More

Laravel Forum 6.0 released

Hi all!

I've spent the past few weeks working on a new major release of Laravel Forum. Highlights include:

* Laravel 11 support
* A new UI preset system (similar to Laravel's Starter Kits)
* A new Livewire-powered, Tailwind-styled UI preset supporting dark mode




You can find an up-to-date live demo here:
https://laravel-forum.teamteatime.net/

I also overhauled the site where the docs are hosted. You can find them here:
https://www.teamteatime.net/docs/laravel-forum/6.x/general/

Feel free to ask questions here, or if you encounter any bugs, please open an issue!

Thank you! submitted by /u/DevRiari
[link] [comments]

Read More

The IEDA software cannot run the Vue project, and the IDEA shows that no executable file was found in $PATH

电脑的path环境在.zshrc中，把node的bin文件路径也添加到了zshrc中，终端也可以查看到node的版本，idea还是显示在path中未找到可执行的文件


运行报127错
env: node: No such file or directory


进程已结束，退出代码为 127


enter image description here


enter image description here


问下各位大佬怎么解决


enter image description here


enter image description here

Read More

A website displays attachments(files) either as pdf, XMl (XRBL) . I want to see info in XRBL files the same way as i see pdf and not the actual text

A website display attachments(files) as either as pdf , XMl (XRBL) . I want to see info in XRBL files the same way as i see pdf and not the actual. Is there any chrome extension for the same. Ideally I want to click on it and when it open it in browser,some way in the browswer itself so that I can make sense from it. If not possible in browser then how best to see the contents in a visual format rather than as text.



https://nsearchives.nseindia.com/corporate/xbrl/KANDARP_05042024142508_CLOSURE_TRADING_WINDOW_1081236_05042024022507_WEB.xml

Read More

I am trying to make a console.log but it does not work in my app

I'm building a react app and when I add a console.log, there is not output.


Help, please.


I'm using react, vite, chrome and edge

Read More

The docker client must be run elevated to connect

When I am trying to built docker app, I am getting below error. Command I am running is docker build -t node_curd_exe .




error during connect: Post
http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.40/build?buildargs=%7B%7D&cachefrom=%5B%5D&cgroupparent=&cpuperiod=0&cpuquota=0&cpusetcpus=&cpusetmems=&cpushares=0&dockerfile=Dockerfile&labels=%7B%7D&memory=0&memswap=0&networkmode=default&rm=1&session=h3q9gxeprezyco28agiqe9jp2&shmsize=0&t=node_curd_exe&target=&ulimits=null&version=1: open //./pipe/docker_engine: The system cannot find the file specified. In the default daemon configuration on Windows, the docker client must be run elevated to connect. This error may also indicate that the docker daemon is not running.



Anything else I can do ?

Read More