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
The proposed solution here would be to somehow rebuild the dist/colyseus.js file whenever a new @colyseus/schema version gets released. Probably doable through GitHub actions.
Publish colyseus.js to NPM
Upload Construct 3 Plugin
Upload Cocos Creator Plugin
The text was updated successfully, but these errors were encountered:
I was just passing by this repo and found this issue. Unsolicited advice: At PixiJS, we use a monorepo and have a "bundle" type of package (pixi.js is one). You could split everything colyseus.js into other packages and then colyseus.js just re-exports the components (i.e. @colyseus/* stuff). Each time you publish your monorepo, all dependents of changed packages will get republished. That includes your bundle.
The bundled
dist/colyseus.js
contains both the Colyseus SDK and@colyseus/schema
bundled together.Problem
When hotfixes are applied to
@colyseus/schema
the bundledcolyseus.js
can get behind.Places where the bundled
dist/colyseus.js
is used currently are:colyseus.js/package.json
Line 23 in 9b9b718
Solution
The proposed solution here would be to somehow rebuild the
dist/colyseus.js
file whenever a new@colyseus/schema
version gets released. Probably doable through GitHub actions.colyseus.js
to NPMThe text was updated successfully, but these errors were encountered: