|
1 | 1 | # Hlambda (/hlæmdə/; hλ;) [Hyper Lambda]
|
2 | 2 |
|
| 3 | +<span><a href="https://www.patreon.com/bePatron?u=70751523" title="Donate to this project using Patreon"><img src="https://img.shields.io/badge/patreon-donate-green.svg" alt="Patreon donate button" /></a></span> |
| 4 | +<span><a href="https://github.com/hlambda/hlambda-core/actions/workflows/publish-docker-image.yml" title="Publish Docker Image"><img src="https://img.shields.io/github/workflow/status/hlambda/hlambda-core/Publish%20Docker%20image" alt="Publish Docker Image" /></a></span> |
| 5 | +<span><a href="https://hub.docker.com/r/hlambda/hlambda-core" title="Docker Image"><img src="https://img.shields.io/docker/image-size/hlambda/hlambda-core/latest" alt="Docker Image Size" /></a></span> |
| 6 | +<span><a href="https://github.com/hlambda/hlambda-core/blob/master/LICENSE.md" title="License"><img src="https://img.shields.io/github/license/hlambda/hlambda-core" alt="License" /></a></span> |
| 7 | + |
3 | 8 | ## What is Hlambda (/hlæmdə/) [Hyper Lambda]
|
4 | 9 |
|
5 | 10 | Hlambda is ECMAScript meta API service. That means that it offers simple ways to deploy ECMAScript code to local or remote servers.
|
6 | 11 |
|
7 |
| - |
| 12 | +<a href="https://hub.docker.com/r/hlambda/hlambda-core" title="Docker Image"> |
| 13 | + |
| 14 | +<picture> |
| 15 | + <source media="(prefers-color-scheme: dark)" srcset="https://www.hlambda.io/assets/hlambda-logo-light.png"> |
| 16 | + <source media="(prefers-color-scheme: light)" srcset="https://www.hlambda.io/assets/hlambda-logo-dark.png"> |
| 17 | + <img alt="Hlambda Banner" src="https://www.hlambda.io/assets/hlambda-logo-dark.png"> |
| 18 | +</picture> |
| 19 | + |
| 20 | +</a> |
8 | 21 |
|
9 | 22 | It is the implementation of the idea to load your ECMAScript code as configuration (metadata). With Hlambda you can easily create a microservice that can load arbitrary code configuration.
|
10 | 23 |
|
@@ -45,15 +58,14 @@ You can check ["Getting started"](https://www.hlambda.io/getting-started/) on ho
|
45 | 58 |
|
46 | 59 | - Importing npm packages that are used by the Hlambda Core like;
|
47 | 60 |
|
48 |
| - - "colors": "1.4.0", |
49 |
| - - "hlambda": "^0.0.3", |
| 61 | + - "colors": "1.4.0" |
50 | 62 |
|
51 |
| -can cause known issues... like the disabling inherited colors prototype chain unless FORCE_COLOR is set to true. |
52 |
| - |
53 |
| -Exporting errors in hlambda if imported can also cause it to not be visible in the list of errors or constants on the hlambda server. |
| 63 | +can cause known issues... like the disabling inherited colors prototype chain unless `FORCE_COLOR` is set to true. |
54 | 64 |
|
55 | 65 | Until addressed this has a simple hotfix to just remove that package from the list of dependencies in your hlambda app, before applying metadata.
|
56 | 66 |
|
| 67 | +- Some of the packages are provided with the hlambda core, but that does not necessarily mean you should use them, you can use your version of packages defined for your hlambda apps. |
| 68 | + |
57 | 69 | ## Notice
|
58 | 70 |
|
59 | 71 | ```
|
|
0 commit comments