[2.x] Should nprogress remain a dependency?

[NickSdot]

I wanted to open this to ensure awareness and have it tracked.

The core package requires nprogress which seems more or less abandoned. The last 0.2.0 release on npm was 9 years ago.

4 years ago there was an attempt to release 1.0.0, which was tagged on GitHub but never made it as "latest" to npm.

Issues and merge requests are ignored; new packages spammed.

Not sure how I feel about such a dependency in general. Additionally, not everyone needs progress bars. And support for the navigation api (native spinners, yay!) in all major browsers seems only months away.🤏

I was wondering if Inertia v2 would be a good moment to drop mentioned dependency and make it (and it's Inertia wrapper) optional?

[SuperDJ]

Also many UI packages already include their own progress bar.

[NickSdot]

Also many UI packages already include their own progress bar.

Good point! And who still really wants it from Inertia can use the core-independent inertiajs/progress with no hustle (but still stuck on the abandoned nprogress).