Sudhir Mitharwal
Sudhir Mitharwal
Same thing here. Lumen has some issues with loading assets from vendor due to it fast router (I guess.) What I did was, added a `post-install-cmd` script in the `composer.json`...
@karthikavkannan24 Please try this. ```php // Somewhere in your middleware or any other place /** * @OA\SecurityScheme( * type="http", * description="Login with email and password to get the authentication token",...
@dvdbot This is the intended behaviour. Basically, what `*:publish*` all does is, it copies something from `vendor` to the publishing folders. So we have 3 commands `:publish-config`, `:publish-views` and `:publish`....
Yeah.. docs mention to do `:publish` in step after making configuration changes. That's a bit misleading. You are right. Anyway. Hope my comment helped.
@Stuey61296 and everyone using for React-18, you might want to look at https://github.com/final-form/react-final-form/issues/1009.
Published fix in [`v3.1.4`](https://github.com/final-form/react-final-form-arrays/releases/tag/v3.1.4).
I tried patch-packages as well but it is not the right tool so I went with the --legacy-peer-deps. I didn't know about the override thing. Thank you so much for...
> I still had trouble when manually updating the peer dependency in react-final-form-arrays to include 18.x, so I'm not sure if that's all that has to change. BTW, @bdbvb What...
Hi @aaa-paul What @rbuetzer meant was to patch the final-form package inside the `node_modules` folder. To ensure that is stays patched for further installs, we can use the [patch-package](https://www.npmjs.com/package/patch-package). Here...