New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The state of this repository/package #3383
Comments
Please don't get this wrong, but let me just directly mention @thecrypticace as he is the last person who merged/committed to this repository. I am an open source maintainer myself and can definitely respect if one doesn't want or can't contribute to a specific open source project any more for whatever reason - but an official statement would still be nice, so at least new people don't waste their time on a tool which doesn't get updated any more. |
I tried using Vite, but it didn't fit into my workflow. I only managed to integrate Vite with Laravel; however, outside of Laravel, I couldn't seamlessly incorporate it into my workflow. On the other hand, Laravel Mix integrates smoothly into all of my projects. It still functions well, but I would appreciate an up-to-date version that removes legacy code and aligns it with Vite's capabilities |
I guess no answer is also an answer... |
wasn't it @jnoordsij ? still, is sad the status of this... maybe ask in laravel discord or somebody could do a fork |
The last commit is mine, but it's a PR not merged by me. I'm not in any way officially related to this project, so afraid I can't help out here. |
so looking through the open issues as well as the open pull requests it is pretty obvious, that this package is not actively maintained any more (v6 was released 3+ years ago, last commit merged was 1 year ago)
It's only a matter of time till the NodeJS runtime starts dropping stuff this package (or its dependencies) relies on and basically breaks this package.
Looking at the current recommended Laravel JS/CSS build system it seems, that Vite is the new hot system in town. There is indeed a Migration guide to help switching, but does this mean this package is actually dead?
I assume there are certainly enough non Laravel devs using this package to have a "Webpack for the 80% use case" as the website states.
Just wanted to ask what the official statement here is since we thought switching to this package meant we have nothing to worry about in the modern crazy JS world we live in for years to come but looking at the current state we are forced to switch again...
The text was updated successfully, but these errors were encountered: