Closed alexandernanberg closed 2 years ago
This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.
🔍 Inspect: https://vercel.com/pmndrs/use-cannon/5kWXGMGX8saST1y7GHSStbDZjeqE
✅ Preview: https://use-cannon-git-fork-alexandernanberg-make-cannon-88e339-pmndrs.vercel.app
We need cannon-es
inlined for the worker where the cannon code is actually run.
I will say that we can move cannon-es
to a devDependency since it is already bundled in the distribution.
Oh makes sense 👍
Found out while trying to debug some things that
cannon-es
andcannon-es-debugger
are inlined in theuse-cannon
bundle. Not sure if this is intentional or not?They are listed as dependencies of this package so consumers will download the code twice on npm install. It also makes it harder to debug things locally, e.g. I tried to change some things in
node_modules/cannon-es
but didn't understand why the changes didn't go throughWhen building we get this warning
not sure if we should care about it or not