functionscript-server
FunctionScript
| functionscript-server | FunctionScript | |
|---|---|---|
| - | 5 | |
| 22 | 1,609 | |
| - | 0.6% | |
| 0.0 | 5.3 | |
| 12 months ago | 7 months ago | |
| JavaScript | JavaScript | |
| MIT License | MIT License |
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.
functionscript-server
We haven't tracked posts mentioning functionscript-server yet.
Tracking mentions began in Dec 2020.
FunctionScript
- FunctionScript: API gateway and framework to turn functions into web services
-
WebGPT: Customizable Website Chat Agent built in Node.js / JavaScript (x-post r/node)
This is no different than a repo that works on Vercel or Cloudflare workers. It is locally runnable — our gateway specification is open source at https://github.com/acode/functionscript . You can use this locally yourself via our command line tools at https://github.com/acode/cli .
-
Solving Coding Challenges with JavaScript Functions on Autocode
It's that simple to deploy reusable functions through Autocode! If you would like to dive deeper into Autocode's framework, check out FunctionScript on Github!
-
The Railsification of SaaS
You're half-right - we have a specification called FunctionScript [0] that can act as what's basically a universal translation layer for any API. You just generate a proxy to it using FunctionScript. So it's possible to add GraphQL APIs to our stdlib, it's just not convenient right now. All of Shopify is a GQL API, for example.
The reason we don't support GQL APIs natively is because we designed Autocode to follow the best practices of the top API companies we knew; Twilio and Stripe. Both companies designed their SDKs in a way that feels intuitive: a call to their API is achieved via a namespaced function call -- it's very Railslike. Everything available in our stdlib follows that convention as we felt it was the most intuitive approach to API / SDK design.
[0] https://github.com/FunctionScript/FunctionScript
-
An Introduction to Scraping (Almost) Anything With Puppeteer and Node.js
Note: To make the screenshot return as an image rather than just binary data, we must pass back the proper Content-Type header. The above code is an example of how to do this in Autocode with the object.http return type. To return other types of data, you'll need to remove the return type or change the return type to match the type of data you're returning. For more information, you can read about the FunctionScript specification Autocode uses for parameters and return types.
What are some alternatives?
lcbo-api - A crawler and API server for Liquor Control Board of Ontario retail data
pixelmatch - The smallest, simplest and fastest JavaScript pixel-level image comparison library
owen-wilson-wow-api - JSON API for actor Owen Wilson's 'wow' exclamations in movies
express-faas-rpc-example - How to write a FaaS in NodeJS with less than 100LoC by using MetaCall.
KeyQL - A language and specification for building data queries using key-value pairs
Strapi - 🚀 Strapi is the leading open-source headless CMS. It’s 100% JavaScript/TypeScript, fully customizable and developer-first.
lib - Autocode CLI and standard library tooling