You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,4 +1,4 @@
1
-
# reason-node
1
+
# reason-nodejs
2
2
3
3
## Project Status
4
4
@@ -26,7 +26,7 @@ This library is still under construction. Some of the core design details are st
26
26
Using the [yarn](https://yarnpkg.com/) package manager:
27
27
28
28
```shell
29
-
yarn install reason-nodejs
29
+
yarn add reason-nodejs
30
30
```
31
31
32
32
Using the [npm](https://www.npmjs.com/) package manager:
@@ -37,12 +37,12 @@ npm i reason-nodejs
37
37
38
38
## Goal of this library
39
39
40
-
Help all Reason Node.js apps and libaries to be built faster by reducing the time spent on hand written bindings.
40
+
Help all Reason Node.js apps and libraries to be built faster by reducing the time spent on hand written bindings.
41
41
42
42
## Non-Goals
43
43
44
44
- Have 100% coverage of Node.js api surface - Due to lack of man power for testing and maintaining, we should only have enough surface to cover all common use cases. But we should have enough coverage that developers only rarely have to write a custom binding.
45
-
- Ensure all APIs are idiomatic Reason and 100% typesafe - This library should be as barebones as possible to allow for minimal context switching between offical Node.js documentation and the Reason equilvalent. And due to the dynamic nature of the JS API, bending it to be idiomatic Reason will lead to a ton of bikeshedding in design as well as sacrificing maintainability.
45
+
- Ensure all APIs are idiomatic Reason and 100% typesafe - This library should be as low-level as possible to allow for minimal context switching between offical Node.js documentation and the Reason equilvalent. And due to the dynamic nature of the JS API, bending it to be idiomatic Reason will lead to a ton of bikeshedding in design as well as sacrificing maintainability.
0 commit comments