# 6.1 Imports and ops

In the previous chapter, we explored the execution of a simple "hello world" program in Deno, examining key concepts in depth. The program's simplicity was intentional, allowing us to focus on understanding Deno's functionality rather than the program itself.&#x20;

Our exploration covered a range of crucial topics, including:

* The execution command known as "Run"
* The central entity referred to as the "Main Worker"
* The mechanism responsible for loading modules
* Visualization of the module relationships through the module graph
* The component handling the retrieval of files
* The JavaScript Runtime, which is pivotal for execution
* The multifaceted process of module loading
* The intricate evaluation procedure of these loaded modules
* And many other interconnected elements.

This chapter marks a new stage in our exploration. We will build on our initial "hello world" example by adding imports, synchronous and asynchronous operations. This will significantly improve our understanding of how imports work in Deno's framework and how Deno and the V8 engine manage operations.&#x20;

Note that this chapter is a direct continuation of the previous one. With a solid foundation in place, we will focus on new concepts and insights, rather than revisiting the basics.

## Chapter contents

{% content-ref url="/pages/-MNCUvUoUHmoc0V5r1N-" %}
[6.1 Imports and ops](/internals-of-deno/import-and-ops/console-print-with-delay.md)
{% endcontent-ref %}

{% content-ref url="/pages/-MNCVdL24chfhbmGTIYS" %}
[6.2 Hello world program v2](/internals-of-deno/import-and-ops/basic-console-print-with-delay.md)
{% endcontent-ref %}

{% content-ref url="/pages/-MNFGSYIb\_07MYeVFp4S" %}
[6.3 Module graph with imports](/internals-of-deno/import-and-ops/building-module-graph.md)
{% endcontent-ref %}

{% content-ref url="/pages/-MPWQh9nYKb8p0ToY5Io" %}
[6.4 Transpile](/internals-of-deno/import-and-ops/5.4-transpile.md)
{% endcontent-ref %}

{% content-ref url="/pages/-MNFKjcKRLw3mTh\_w8p5" %}
[6.5 Registration and instantiation](/internals-of-deno/import-and-ops/registration-and-instantiation.md)
{% endcontent-ref %}

{% content-ref url="/pages/-MPaLXQmvMiMVuoNtKdz" %}
[6.6 Registration of ops](/internals-of-deno/import-and-ops/5.6-registration-of-ops.md)
{% endcontent-ref %}

{% content-ref url="/pages/-MNGd6OlBkGucnuDwJPr" %}
[6.7 Evaluate module](/internals-of-deno/import-and-ops/evaluate-module.md)
{% endcontent-ref %}

{% content-ref url="/pages/-MPc0H2\_uVb4715vQBXE" %}
[6.8 Sync OPs](/internals-of-deno/import-and-ops/5.8-sync-op.md)
{% endcontent-ref %}

{% content-ref url="/pages/ia30HhDWwFlzg3Edeg9y" %}
[6.9 Debug logs](/internals-of-deno/import-and-ops/6.9-debug-logs.md)
{% endcontent-ref %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://choubey.gitbook.io/internals-of-deno/import-and-ops/console-print-with-delay.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
