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
Some of the modern libraries like solid-js now rely on the exports entry in package.json to import the correct code for different environments (node, browser, etc).
Most of the tools such as Parcel, Rollup, Vite, etc support these entries, but Jasmine doesn't. Could you the support for that?
That sounds like it could be useful. The catch is that the jasmine node module doesn't have a particularly well-documented public API at this point, so adding exports would likely be a breaking change. (Contrast jasmine-core, which does have a documented public API but isn't packaged in a way that makes exports useful.) We'll take another look at this when we get close to the next major release.
Some of the modern libraries like
solid-js
now rely on theexports
entry inpackage.json
to import the correct code for different environments (node, browser, etc).Most of the tools such as Parcel, Rollup, Vite, etc support these entries, but Jasmine doesn't. Could you the support for that?
Here is more information about
exports
:https://nodejs.org/api/packages.html#packages_subpath_exports
https://medium.com/swlh/npm-new-package-json-exports-field-1a7d1f489ccf
The text was updated successfully, but these errors were encountered: