> For the complete documentation index, see [llms.txt](https://docs.sacruda.nl/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sacruda.nl/developers/your-apps-code/the-basics.md).

# The basics

The CLI generates a Javascript file for your project: `process.js`. This file contains your app's process. Here you'll end up writing the base logic for your application.

<pre class="language-typescript"><code class="lang-typescript">class proc extends ThirdPartyAppProcess {
  constructor(pid, parentPid, app, operationId, workingDirectory, ...args) {
    super(pid, parentPid, app, operationId, workingDirectory);
  }
}

<a data-footnote-ref href="#user-content-fn-1">return proc;</a>
</code></pre>

{% hint style="warning" %}
In Sacruda version 7.0.10 and onwards, the way TPAs are invoked has changed. Instead of having a `main.js` that calls `runApp` or `runAppDirect` to spawn the process, applications are now expected to return the process class directly from process.js. \
\
The old implementation will keep working until all apps are ported over to the new format. The v7cli has been updated to reflect this change.
{% endhint %}

{% hint style="danger" %}
The code inside `main.js` runs *outside the process scope*, meaning that that code can't be associated with any running process. See it as the middleman: an intermediary period between the User Daemon and your app's process. You're expected to write any actual app logic inside class methods, anything outside the classes is considered preparative code, initializers before the actual app process is able to be spawned.
{% endhint %}

From here, you have a choice to make. Do you want to develop a traditional Sacruda application? Then go to [Third-party app process](https://docs.sacruda.nl/developers/your-apps-code/third-party-app-process.md). If you want a regular process that modifies Sacruda in a different way than an application (like adding something to the desktop or shell), you might want to opt for a [Basic third-party process](https://docs.sacruda.nl/developers/your-apps-code/basic-third-party-process.md).&#x20;

[^1]: Return the process directly from process.js so that ArcOS can find it
