Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: ARCHITECTURE.md #737

Merged
merged 7 commits into from
May 23, 2024
Merged

chore: ARCHITECTURE.md #737

merged 7 commits into from
May 23, 2024

Conversation

mmastrac
Copy link
Contributor

@mmastrac mmastrac commented May 10, 2024

This is a first pass at ARCHITECTURE.md, a high-level overview of how deno_core works.

@mmastrac mmastrac changed the title chore: ARCHITECTURE.md [WIP] chore: ARCHITECTURE.md May 14, 2024
ARCHITECTURE.md Outdated Show resolved Hide resolved
Comment on lines +10 to +11
Each `extension` consists of a number of JavaScript- or TypeScript-language
ECMAScript modules, as well as a number of `op`s. This module code is loaded
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Mention that code-only and op-only extensions are allowed?


When the runtime is initialized, it creates a V8 isolate and context, and then
instantiates the provided extension code and ops into the new context. The ops
are provided in a special, virtual module that can be imported from the
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Show example of importing the ops virtual module?

Co-authored-by: Bartek Iwańczuk <biwanczuk@gmail.com>
@mmastrac mmastrac merged commit e9643e7 into denoland:main May 23, 2024
18 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants