This doesn't happen with regular use since the folder name will always be equal to the package.json name, and tools.edn will always be equal to the folder name.
However, when testing locally by using symlinks you may end up with a folder and tools.edn name that differs from the package.json name. This is also difficult to debug, since it's obvious to check that the tools.edn and folder name match, but not obvious to check the package.json name.
We should use the tools.edn name when determining the path to the bundle instead, so a differing package.json name won't have any effect.
This doesn't happen with regular use since the folder name will always be equal to the package.json name, and tools.edn will always be equal to the folder name.
However, when testing locally by using symlinks you may end up with a folder and tools.edn name that differs from the package.json name. This is also difficult to debug, since it's obvious to check that the tools.edn and folder name match, but not obvious to check the package.json name.
We should use the tools.edn name when determining the path to the bundle instead, so a differing package.json name won't have any effect.