You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since matter-tools is only used is the demo, it should be a devDependency.
Currently, when the matter-collision-events package is installed it will pull along matter-tools and all its dependencies. This is suboptimal because it results in a bigger node_modules directory and some of matter-tools dependencies take ages to get built coughnode-sasscough.
Also, the node-sass that matter-tools uses' build process fails with Node.js 12 at the moment, so matter-collision-events can't be used in a Node.js 12 environment. Of course this issue also needs to be addressed separately, but at least it would not impact matter-collision-events users.
The text was updated successfully, but these errors were encountered:
Since
matter-tools
is only used is the demo, it should be a devDependency.Currently, when the
matter-collision-events
package is installed it will pull alongmatter-tools
and all its dependencies. This is suboptimal because it results in a biggernode_modules
directory and some ofmatter-tools
dependencies take ages to get built coughnode-sass
cough.Also, the
node-sass
thatmatter-tools
uses' build process fails with Node.js 12 at the moment, so matter-collision-events can't be used in a Node.js 12 environment. Of course this issue also needs to be addressed separately, but at least it would not impactmatter-collision-events
users.The text was updated successfully, but these errors were encountered: