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 recently, an NPM artifact doesn't provide a bundled version anymore.
It was done since parsing of Protobuf messages wasn't working in the bundled version. The reason is that the import of TypeParsers always references a file from the unbundled version:
// The import generated by Spine's Protobuf Plugin for JS.letTypeParsers=require('spine-web/client/parser/type-parsers.js').default;
Instead, in pb.js files used in the bundled version should be import TypeParsers from the bundled version too:
// Import `TypeParsers ` from a bundle.letTypeParsers=require('spine-web/bundle').default;
There is no easy way to adjust these imports depending on the used version (bundled/unbundled). Commonly, the end user can bundle sources on its own, so the absence of the bundled version is not crucial.
After the root issue will be resolved, we should enabled the bundle publishing again, by reverting these changes.
The text was updated successfully, but these errors were encountered:
Since recently, an NPM artifact doesn't provide a bundled version anymore.
It was done since parsing of Protobuf messages wasn't working in the bundled version. The reason is that the import of
TypeParsers
always references a file from the unbundled version:Instead, in
pb.js
files used in the bundled version should be importTypeParsers
from the bundled version too:There is no easy way to adjust these imports depending on the used version (bundled/unbundled). Commonly, the end user can bundle sources on its own, so the absence of the bundled version is not crucial.
After the root issue will be resolved, we should enabled the bundle publishing again, by reverting these changes.
The text was updated successfully, but these errors were encountered: