-
Notifications
You must be signed in to change notification settings - Fork 5
Update npm root paths for relevant repos #524
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
All repos needs to fixed. We are using |
Including @amydevs when you are working on any of the repos, you should fix them when you see them too. |
I've done it for @amydevs needs to do it for the new |
Done for @amydevs any update here? |
Done for |
Done for |
Not yet done for |
Done for |
@amydevs can you identify that this is going to be done for |
Done for |
TBD:
|
@amydevs Do you see this notification now? |
done for |
I've done for |
I've done it for |
Done for js-logger. |
Remaining repos is js-db and js-encryptedfs, these 2 use quite a few changes... so it would be interesting to see how they play out. |
For js-db, it is being tracked in MatrixAI/js-db#62. The js-encryptedfs should be a simple upgrade, but it does depend on the js-db being fixed first. Afterwards, this can be closed. |
Was done here: MatrixAI/js-encryptedfs#80. Will be released as 3.5.7. All libraries done. Closing this. Well except the TypeScript Demo native but that's not really relevant anymore with js-db and js-quic being representative native projects. |
@tegefaulkes Polykey deps will need to be all updated however all libraries should be updated with the latest now and confirmed to work on node v18. |
Specification
the
npm bin
command no longer works since it has been deprecated. This means ourshell.nix
no longer adds our bin commands for the project to the local environment. This needs to be fixed for some of our repos. I think any repo that defines bin commands in the package.json?To fix this the following changes need to be replicated. 78a9faa
Additional context
Tasks
The text was updated successfully, but these errors were encountered: