I'm not sure what kind of SharePoint List solution package you're talking about, either sandboxed solution (deprecated) or the new SPFx package. Aside from that, there are many ways to deploy SharePoint List without solution package, such as with PowerShell script or manually create just like Austin mentioned before.
The latest procedure of packaging SharePoint List is described in the Microsoft site via SPFx package, under assets. Do note that this method is slower, and NOT very popular unless if you are restricted to deploy or create site or probably just for the sake of documentation of the solution.
- Create an SPFx package (if you don't have one) or modify existing if you're already have for your solution.
assets folder under
assets folder and define your SharePoint List schema there.
- Add another XML for elements and upgrade solutions (in case you want to update the SharePoint List schema in the future).
- Modify your package-solution.json to include those schemas.
- Package it with
gulp package-solution and give the generated solution *.sppkg to SharePoint Admin to deploy.
If you know how to build SharePoint List XML manifest and elements, you're good to go. The method derived from the exact same schema when we used to have on-premises solution package to deploy webparts. If not:
The last 2 links are similar in nature but complementing each other. I do recommend read both.