extensions
extensions copied to clipboard
Add new extension "NixPkgs Search"
Description
Add a new extension "NixPkgs Search". This extension performs a search on NixPkgs using NixOS's Elasticsearch API.
Resolved error
When I ran npm run build I always get the following error:
$ npm run build
> build
> ray build -e dist
info - entry points [src/index.tsx]
src/index.tsx:224:7 - error TS2739: Type 'AbortSignal' is missing the following properties from type 'AbortSignal': addEventListener, removeEventListener
224 signal: signal,
~~~~~~
Found 1 error in src/index.tsx:224
TypeScript check failed (exit status 2)
Is this safe to be ignored?
Screencast
https://user-images.githubusercontent.com/37664775/186431068-371671cd-ec30-43fd-b11d-8d2f24827806.mov
Checklist
- [x] I read the extension guidelines
- [x] I read the documentation about publishing
- [x] I ran
npm run buildand tested this distribution build in Raycast - [x] I checked that files in the
assetsfolder are used by the extension itself - [x] I checked that assets used by the
READMEare placed outside of themetadatafolder
Congratulation on your new Raycast extension! :rocket:
We will review it shortly. Once the PR is approved and merged, the extension will be available on the Store.
The extension icon is provided in CC-BY. Where should I put the licence if I cannot use SVG? (Currently the license is written inside SVG file)
I'll fix the icon format and also add some screenshots.
Converted SVG logo into PNG, and added LICENSE file to specify the license of the logo. Also added a screenshot.
Oh, node-fetch version was the problem! It seems Raycast's extension template have to be updated
yeah, this update was the culprit. 😅
We're looking into a proper fix, but for now I've pinned node-fetch to an older version.
I pushed 2 commits to fix a bug which is rare to be occurred. This PR is ready to be merged. Are there anything preventing it from merging?
🎉
Published to the Raycast Store: https://raycast.com/aiotter/nixpkgs-search
Thanks! I'm wondering what is the best shortcut keys. I'll keep using it and seek for better ones. If anyone have some idea about it, please share your thought.