1st issue: Bare import for @sasjs/utils doesn't work
Currently, if in any place in adapter @sasjs/utils import is used as bare, the adapter Is unable even to load. (eg. in Data Controller)
The workaround we are using is deep imports @sasjs/utils/some/path.
That is a huge issue since any external contributor would have problems and would not even know why. Even @YuryShkoda lost too much time on it, just because it is unclear what the issue is.
2nd issue: When the adapter is built with development mode, it fails to load
Very similar to the above issue, the error happens because of the @sasjs/utils package, but from the error, it is uncertain as to why. Most likely it has to do with something about how @sasjs/utils is bundled.
How to reproduce webpack development mode issue
- Then run
npm run package:lib
- Install tarball to the client (eg. DC)
1st issue: Bare import for @sasjs/utils doesn't work
Currently, if in any place in adapter @sasjs/utils import is used as
bare, the adapter Is unable even to load. (eg. in Data Controller)The workaround we are using is deep imports
@sasjs/utils/some/path.That is a huge issue since any external contributor would have problems and would not even know why. Even @YuryShkoda lost too much time on it, just because it is unclear what the issue is.
2nd issue: When the adapter is built with development mode, it fails to load
Very similar to the above issue, the error happens because of the
@sasjs/utilspackage, but from the error, it is uncertain as to why. Most likely it has to do with something about how@sasjs/utilsis bundled.How to reproduce webpack development mode issue
npm run package:lib