Package database table 'visits' causes conflict

[sepisoltani]

If an existing Laravel project contains the table with the name of 'visits' , you'll run into trouble !
In my case, I have a table called 'visits' in my application and this package also wants to create a 'visits' table.

A good way to prevent this would be for package to automatically prefix the visits table.