Nova custom tools

I created a custom tool in Nova and I noticed Laravel is using the tool package from the composer vendor directory and not the nova-components directory. My question is what is the best way to update the code in the vendor directory when I make changes to my tool?

Can I config my application so that the tool is loaded from my nova-components directory?

Am I missing something in my development process?

Thank you

bobbybouwmann

6 years ago

Level 88

I'm not sure what you mean with tools in the vendor directory. All new tools should end up in the nova-components directory.

opilo

6 years ago

Best Answer

Level 2

I am developing using Homestead on Windows.

The Problem was that composer failed to create a symlink between my nova-components source and vendor directory and instead mirrored the code. Therefor my changes in nova-components directory was not copied to vendor.

Here's how i fixed the issue. I use windows command line to fire up the virtual machine ( Hometead up). I ran the command line as an administrator and the symlink worked in the composer.

opilo

6 years ago

Level 2

After I installed the tool and ran composer install, the tool was copied to composer's vendor directory and it was loaded from there.

PaulMarshall

6 years ago

Level 12

Hi @opilo I think I might be having the same issue as you, changes to my nova-component custom field work on Homestead but when I deploy to Laravel Vapor and it builds I get the old files when I visit Nova on the live site.

Any advice?

Thanks

Please or to participate in this conversation.