gorilla
webextension-polyfill
gorilla | webextension-polyfill | |
---|---|---|
51 | 18 | |
10,118 | 2,543 | |
- | 1.2% | |
8.9 | 4.7 | |
4 days ago | 6 days ago | |
Python | JavaScript | |
Apache License 2.0 | Mozilla Public License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
gorilla
-
Launch HN: Nango (YC W23) – Open-Source Unified API
Do you leverage https://gorilla.cs.berkeley.edu/ at all? If not, perhaps consider if it would solve some pain for you.
- Autonomous LLM agents with human-out-of-loop
- Show HN: I made a script to scrape your Facebook group
-
Pushing ChatGPT's Structured Data Support to Its Limits
* Gorilla [https://github.com/ShishirPatil/gorilla]
Could be interesting to try some of these exercises with these models.
-
Guidance for selecting a function-calling library?
gorilla
- Gorilla: An API Store for LLMs
-
Show HN: OpenAPI DevTools – Chrome ext. that generates an API spec as you browse
Nice this made me go back and check up on the Gorilla LLM project [1] to see whats they are doing with API and if they have applied their fine tuning to any of the newer foundation models but looks like things have slowed down since they launched (?) or maybe development is happening elsewhere on some invisible discord channel but I hope the intersection of API calling and LLM as a logic processing function keep getting focus it's an important direction for interop across the web.
[1] https://github.com/ShishirPatil/gorilla
-
RestGPT
"Gorilla: Large Language Model Connected with Massive APIs" (2023) https://gorilla.cs.berkeley.edu/ :
> Gorilla enables LLMs to use tools by invoking APIs. Given a natural language query, Gorilla comes up with the semantically- and syntactically- correct API to invoke. With Gorilla, we are the first to demonstrate how to use LLMs to invoke 1,600+ (and growing) API calls accurately while reducing hallucination. We also release APIBench, the largest collection of APIs, curated and easy to be trained on! Join us, as we try to expand the largest API store and teach LLMs how to write them!
eval/:
- Calling APIs with Natural Language
-
Shishir Patil: Teaching AI to Use APIs with Gorilla LLM – Humans of AI Podcast
Humans of AI Podcast #7
An amazing conversation with Shishir Patil the creator of the Gorilla LLM, a large language model specifically trained to use APIs!
Shishir is currently a 5th year PhD student at the University of California, Berkeley whose work broadly covers ML-Systems, LLMs, Edge-ML, and Sky computing.
Definitely give the episode a listen to hear Shishir's story.
And to read more about #GorillaLLM, check out the project page!
https://gorilla.cs.berkeley.edu
webextension-polyfill
-
Show HN: Chrome Reaper
Porting this extension to Firefox should be relatively straightforward using the webextension polyfill: https://github.com/mozilla/webextension-polyfill
-
Show HN: OpenAPI DevTools – Chrome ext. that generates an API spec as you browse
Firefox maintain a library for unified extension API https://github.com/mozilla/webextension-polyfill
Their type definition for HAR request isn't exported https://github.com/DefinitelyTyped/DefinitelyTyped/blob/mast...
-
can you convert a simple firefox addon to be used with chrome?
best is to use https://github.com/mozilla/webextension-polyfill
-
Browser Extension with Blazor WASM - Cross-Browser Compatibility
The Browser Extension Working Group at W3.org proposes the web standards based on the Chrome extension manifest, which supports all web browsers. Based on that proposal, Mozilla has released the Browser Extension Polyfill library that supports the modern promise pattern instead of callback. Therefore, if you import this polyfill library, theoretically, your Chrome extension quickly turns into the browser extension that runs on multiple browser engines.
-
IWTL how to make simple chrome extensions.
And the biggest tip that i received late. Use Typescript type by Mozilla to make your development much easier(autocomplete, inline docs etc): https://github.com/mozilla/webextension-polyfill
- Show HN: Plasmo – a framework for building modern Chrome extensions
-
It’s Like GPT-3 but for Code–Fun, Fast, and Full of Flaws
I've written extensions before and Firefox has a very good polyfill [0] that makes it quite easy to write extensions for all browsers. It does get a bit trickier if you also want to incorporate TypeScript [1] or React however.
[0] https://github.com/mozilla/webextension-polyfill
[1] https://github.com/Lusito/webextension-polyfill-ts
-
Ask HN: Browser-extension creators, how do you write for multiple browsers?
I used WebExtension polyfill[0] when adapting my FF addon to Chrome and admittedly all the intricate differences between APIs still costed me half a day of work.
I managed to have it done with only a few places where I branch on navigator.vendor, but If I wanted to ship different versions to AMO and CWS, I'd make use of something like DefinePlugin[1] for webpack to include/exclude code based on build target.
[0] https://github.com/mozilla/webextension-polyfill/
[1] https://github.com/webpack/docs/wiki/list-of-plugins#definep...
-
Creating a browser extension for Safari and Chrome
Initially I created wrapper functions to convert Chrome functions that require callback to return promise instead. The better approach, as I found out later, is probably to use webextension-polyfill from Mozilla and its types.
-
Firefox Addons Unable to Update, Undisclosed AMO Issues
I mean, the browser apis are close (and Mozilla still has much better documentation) but there are a LOT of edges cases where behavior diverges.
Frankly - I'm a little peeved that Optional permissions in Firefox are STILL broken - The prompt can only be triggered in response to a user action, and Firefox blows the fuck up if you put a promise anywhere in between the user click and the call to the api. Which is hugely ironic, since Mozilla is the one pushing to move all the webext APIs to be promise based (and provides a nice helpful library for Chrome/Edge/Safari support: https://github.com/mozilla/webextension-polyfill) which... doesn't work on their platform. Doubly ironic, since the result is that most FF extensions just ask for more permissions up front, which is exactly the opposite of what you'd want in the "secure/private" world Mozilla claims they're pushing towards.
What are some alternatives?
DB-GPT - AI Native Data App Development framework with AWEL(Agentic Workflow Expression Language) and Agents
esbuild-react-chrome-extension - Simple chrome extension with React and Typescript, bundled by esbuild
Voyager - An Open-Ended Embodied Agent with Large Language Models
browser-extension-svelte - A simple cross-browser extension made with Svelte
gorilla-cli - LLMs for your CLI
uBlock-Safari - uBlock Origin - An efficient blocker for Chromium, Firefox, and Safari. Fast and lean.
Gin - Gin is a HTTP web framework written in Go (Golang). It features a Martini-like API with much better performance -- up to 40 times faster. If you need smashing performance, get yourself some Gin.
plasmo - 🧩 The Browser Extension Framework
GirlfriendGPT - Girlfriend GPT is a Python project to build your own AI girlfriend using ChatGPT4.0
webext-redux - A set of utilities for building Redux applications in Web Extensions.
SuperAGI - <⚡️> SuperAGI - A dev-first open source autonomous AI agent framework. Enabling developers to build, manage & run useful autonomous agents quickly and reliably.
browser-ext-react-esbuild - Browser extension implemented in TypeScript & React and built by esbuild for Chrome, Safari and possibly Mozilla Firefox