In my view, this question may not fit within the usual queries on SO as it leans towards opinions and discussions. Nevertheless, here are my thoughts:
Most libraries provide their source code (often open-source) to aid in debugging. They usually include a .map file as well. You can find a useful post explaining what a map file is here..
Consider this: users who employ your distribution will likely only need to install it once, perhaps during project deployment or initial installation.
Also, consider the size of your distribution. Will it significantly slow down installation time?
Generally, a few MB should not impact performance significantly on modern machines.
Personally, I believe including the source code is beneficial. Understanding how libraries function and being able to troubleshoot errors in your code interacting with the library is valuable to me. However, there may be valid reasons not to include it as well.
tl;dr
- Source code is included for debugging purposes
- Installation speed should not be a major concern unless it is unusually long
- The size of the project shouldn't be an issue unless it is excessively large
- As a developer, I appreciate when projects include the source code, but whether it is "good practice" is subjective and context-dependent