Package subpath './lib/command.js' is not defined by "exports" using jasmine-xml-reporter

[mitaly]

Package subpath './lib/command.js' is not defined by "exports" using jasmine-xml-reporter

[sgravrock]

Command isn't part of the public interface, and it can no longer be accessed as of 4.0. Jasmine is part of the public interface but needs to be accessed through the default export. We added the exports entry, which prevents subpath imports, partly for better compatibility with various tools and partly to reduce the risk of people accidentally depending on private APIs that might change at any time.

Unfortunately, while that change makes it less likely that packages will depend on internal implementation details in the future, it breaks packages like jasmine-xml-reporter that already did so.

(In fairness to the author of jasmine-xml-reporter, that wasn't a particularly unreasonable thing to do back in 2016. We didn't clearly document the public API of the jasmine package back then. And even if we had, the idea that packages should only depend on the documented public interfaces of other packages wasn't well established.)

You can hook up the JUnitXmlReporter from jasmine-reporters yourself in a few different ways:

• You can use Jasmine as a library and then follow the jasmine-reporters documentation.
• You can write a helper file that adds the reporter in the same way.
• If you have a jasmine.js config file (not jasmine.json), you can instantiate the reporter and then add it to the reporters config property.

I hope this helps.