It is never a good idea to update vendor packages. If this is needed for a small number of routes, then simply add the custom route before the resource route(s), e.g.
Route::get('things/active', 'ThingsController@active');
Route::resource('things', 'ThingsController');
If you need it for lots of route definitions, then consider registering a Route macro:
Route::macro('resourceAndActive', function ($uri, $controller) {
Route::get("{$uri}/active", "{$controller}@active")->name("{$uri}.active");
Route::resource($uri, $controller);
});
You would use this similarly to the normal resource route declaration:
Route::resourceAndActive('users', 'UserController');
And it will register the usual resource routes along with an active route. It would probably need to be tweaked to allow for something other then a GET route, and to receive the usual options that the resource route accepts, but this should give you an idea to get started with.