msarca
commented
2 years ago We were the only ones using the closure:// wrapper for almost eight years. After using it for so many years, I believe we've earned the right not to check if others decided to use it too.
Version: 3.6.2
Laravel 8.62.0 added a new dependency and also registers the same wrapper but their code fortunately has a backup check to see if it has already been registered in
stream_get_wrappers(), it would br great if this package did that check to so I can fix the below error I am getting in my application.https://github.com/laravel/serializable-closure/blob/master/src/Support/ClosureStream.php#L172-L177