Props-based splitting is not a common code splitting strategy. The common approaches are: route-based splitting (loading code for different routes on demand), component-based splitting (lazy-loading large components when needed), and vendor code splitting (separating third-party libraries into separate chunks). Props-based splitting, which would mean loading different code based on the props passed to a component, is not a standard pattern and would be impractical to implement efficiently as props can change frequently.