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
I think I'm running into the same issue when trying to add a dependency in the KERI Auth browser extension so I can use its types/interfaces. What I think is going on follows:
Issues Encountered:
dist Directory Missing After Installation:
When installing the package directly from GitHub (e.g., using "signify-polaris-web": "github:weboftrust/polaris-web#main" in my package.json), the dist directory is not present in the node_modules folder. This prevents TypeScript files and interfaces from being imported correctly.
Cause: The prepare script in the package.json currently runs husky but does not trigger a build process. As a result, the project is not built during installation.
Manual Steps Required for Consumption:
Currently, consumers may need to clone the repository, build it manually, or add workarounds in their own project to use polaris-web.
Suggestions for Improvement:
Update the prepare Script to Build Automatically:
Modify the prepare script to include a build step so that the dist directory is created during installation. For example:
"scripts": {
"prepare": "husky && npm run build"
}
To Reproduce
I create this package.json
Then I run
npm install
of that project. Then I try and import anything from that package and it fails. Leading to discovering this:All the files aren't being produced in this package for some reason in npm. @lenkan points out in the vlei-developers meeting that: In this PR https://github.com/WebOfTrust/polaris-web/pull/26/files#diff-7ae45ad102eab3b6d7e7896acd08c427a9b25b346470d7bc6507b6481575d519L12 the package was changed so that it possibly no longer builds as it builds in a post-install script.
This issue is to track this in case anyone else runs into this in the future. Two more logs attached for extra information.
The text was updated successfully, but these errors were encountered: