-
Notifications
You must be signed in to change notification settings - Fork 4.1k
Add ray-boop extension #20108
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
base: main
Are you sure you want to change the base?
Add ray-boop extension #20108
Conversation
- fix lint errors - initial commit
Congratulations on your new Raycast extension! 🚀 You can expect an initial review within five business days. Once the PR is approved and merged, the extension will be available on our Store. |
"@raycast/api": "^1.100.3", | ||
"@raycast/utils": "^1.17.0", | ||
"crypto-js": "^4.2.0", | ||
"he": "^1.2.0", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You might want @types/he
for declarations.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should not be necessary we only use he in the encode/decode files pulled from boop source and these are in JS
- fix lint - remove unused lodash dependency - remove js-base64 - use node crypto instead of crypto-js - revert change log
Thanks for the feedback @LitoMore I've resolved the issues. |
Description
Screencast
Checklist
npm run build
and tested this distribution build in Raycastassets
folder are used by the extension itselfREADME
are placed outside of themetadata
folder