aboutsummaryrefslogtreecommitdiff
path: root/src/js/README.md
diff options
context:
space:
mode:
Diffstat (limited to 'src/js/README.md')
-rw-r--r--src/js/README.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/src/js/README.md b/src/js/README.md
index 82acf7c51..f1eb3c6ca 100644
--- a/src/js/README.md
+++ b/src/js/README.md
@@ -36,7 +36,7 @@ V8 has a [similar feature](https://v8.dev/blog/embedded-builtins) to this syntax
On top of this, we have some special functions that are handled by the builtin preprocessor:
-- `require` works, but it must be passed a **string literal** that resolves to a module within `src/js`. This call gets replaced with `$getInternalField($internalModuleRegistery, <number>)`, which directly loads the module by it's generated numerical ID, skipping the resolver for inter-internal modules.
+- `require` works, but it must be passed a **string literal** that resolves to a module within `src/js`. This call gets replaced with `$getInternalField($internalModuleRegistery, <number>)`, which directly loads the module by its generated numerical ID, skipping the resolver for inter-internal modules.
- `$debug` is exactly like console.log, but is stripped in release builds. It is disabled by default, requiring you to pass one of: `BUN_DEBUG_MODULE_NAME=1`, `BUN_DEBUG_JS=1`, or `BUN_DEBUG_ALL=1`. You can also do `if($debug) {}` to check if debug env var is set.
@@ -57,7 +57,7 @@ export default {
};
```
-Keep in mind that **these are not ES modules**. `export default` is only syntax sugar to assign to the variable `$exports`, which is actually how the module exports it's contents. `export var` and `export function` are banned syntax, and so is `import` (use `require` instead)
+Keep in mind that **these are not ES modules**. `export default` is only syntax sugar to assign to the variable `$exports`, which is actually how the module exports its contents. `export var` and `export function` are banned syntax, and so is `import` (use `require` instead)
To actually wire up one of these modules to the resolver, that is done separately in `module_resolver.zig`. Maybe in the future we can do codegen for it.