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
Each package's UMD build adds a property to self that is different than what the other packages' UMD builds expect; for example:
// in `@tsed/schema/lib/browser/schema.umd.min.js`// e === self, t === factorye.schema=t(e["@tsed/core"],e["change-case"])// in `@tsed/core/lib/browser/core.umd.min.js`// t === self, e === factoryt.core=e()
When @tsed/schema executes in a browser, it looks for self["@tsed/core"], which doesn't exist (although self.core does).
To Reproduce
Use Webpack to bundle @tsed/schema
Execute the bundle in a browser
See an error like e.DecoratorTypes is undefined (where e is supposed to be the exports from @tsed/core)
Expected behavior
No error
Code snippets
No response
Repository URL example
No response
OS
macOS
Node version
Node v18.17.1
Library version
v7.39.0
Additional context
No response
The text was updated successfully, but these errors were encountered:
Describe the bug
Each package's UMD build adds a property to
self
that is different than what the other packages' UMD builds expect; for example:When
@tsed/schema
executes in a browser, it looks forself["@tsed/core"]
, which doesn't exist (althoughself.core
does).To Reproduce
@tsed/schema
e.DecoratorTypes is undefined
(wheree
is supposed to be the exports from@tsed/core
)Expected behavior
No error
Code snippets
No response
Repository URL example
No response
OS
macOS
Node version
Node v18.17.1
Library version
v7.39.0
Additional context
No response
The text was updated successfully, but these errors were encountered: