package.json name different from module name cause panic

[endosama]

Hey!
I started getting some issues when bumping from version 1.0.9 to 1.2.2.
We're currently importing this package in our codebase (monorepo):
https://github.com/teamwalnut/rescript-urql
Which has a rescript-urql name in the package.json but a different name @urql/rescript in the bsconfig.json

When the package is resolved, it's stored with rescript-urql as a key, but when resolving the dependencies in our project, we reference the bsconfig.json name of the module, so @urql/rescript, causing a:

thread '<unnamed>' panicked at src/build/compile.rs:568:17:
Expected to find dependent package @urql/rescript of <my-package>

I can change the package.json name for that project, but I'm not sure if that's the correct behaviour and we should instead rely always only on the name in the bsconfig/rescript.json 🤔

If needed, I can try creating a small environment with the issue or add some tests.
Let me know wdyt 🙏

[jfrolich]

Thanks @endosama, I think the PR makes sense, thanks for the contribution 🙏

[jfrolich]

Let me know if you need a new version release!