> For the complete documentation index, see [llms.txt](https://docs.sealights.io/knowledgebase/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sealights.io/knowledgebase/setup-and-configuration/troubleshooting-faq/node-javascript/js-files-missing-from-build-scan.md).

# JS: Files Missing from Build Scan

### Problem <a href="#problem" id="problem"></a>

I’ve configured my JS project for scanning, but some of the files are not showing up in the coverage report.

When enhanced logging is enabled, errors similar to the following appear in the log:

```
ERROR CIA: Failed to create signature for '/path/to/File.js'. Error 'Unexpected token (30:2)' (className=BuildDiffProcess)
```

### Overview <a href="#overview" id="overview"></a>

This happens when some of the contents of the JS files trying to be scanned contain an unexpected formatting style.

{% hint style="warning" %}
This usually happens when code is transpiled or compiled, but can happen for all JS files regardless of compilation or transpilation!
{% endhint %}

### Solution <a href="#solution" id="solution"></a>

#### Babylon (BabelJS) <a href="#babylon-babeljs" id="babylon-babeljs"></a>

**Define the correct Babylon plugins used by your project:**

1. Identify which Babylon plugins are in use in your project from the following list: <https://babeljs.io/docs/en/plugins>
2. Add the `--babylonPlugins` parameter with the name of the Babylon plugin to the `slnodejs build`command. Some examples:
   1. `slnodejs scan <...> --babylonPlugins estree`
   2. `slnodejs scan <...> --babylonPlugins jsx`


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.sealights.io/knowledgebase/setup-and-configuration/troubleshooting-faq/node-javascript/js-files-missing-from-build-scan.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.