> 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-no-front-end-coverage.md).

# JS: No Front-End Coverage

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

I have instrumented my code and used it however I see no coverage reported for my files.

### Solutions <a href="#solutions" id="solutions"></a>

#### Disable caching in your Browser <a href="#disable-caching-in-your-browser" id="disable-caching-in-your-browser"></a>

In Chrome, open the Developer mode (F12), and check the 'Disable cache option under the Network tab.

<figure><img src="https://4057366433-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAjqTCMRYvHhDgsdPLUnc%2Fuploads%2F1TM34mjYzLwb7VjsYbu7%2Fimage2019-6-20_18-23-27.png?alt=media&amp;token=3eec21e3-7469-4735-ab97-bc22c1035ccd" alt=""><figcaption></figcaption></figure>

#### Validate the Instrumentation and build number in the JS source from the Browser <a href="#validate-the-instrumentation-and-build-number-in-the-js-source-from-the-browser" id="validate-the-instrumentation-and-build-number-in-the-js-source-from-the-browser"></a>

In your Browser, open the source code of your JS page: is there the Sealights' instrumentation code and the right build number?

<figure><img src="https://4057366433-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAjqTCMRYvHhDgsdPLUnc%2Fuploads%2FtzZF9S1OtnGgFIrFEw4P%2Fimage2019-6-23_10-45-51.png?alt=media&amp;token=1b5314a6-b630-4103-a23a-faf52f277392" alt=""><figcaption></figcaption></figure>

#### Validate the application is using instrumented source and not compressed files from the Build stage <a href="#validate-the-application-is-using-instrumented-source-and-not-compressed-files-from-the-build-stage" id="validate-the-application-is-using-instrumented-source-and-not-compressed-files-from-the-build-stage"></a>

* Check JS is not compressed at the Application Server and therefore confirm the instrumented files are the one used

#### Validate the application is using the static instrumented files and not files in memory <a href="#validate-the-application-is-using-the-static-instrumented-files-and-not-files-in-memory" id="validate-the-application-is-using-the-static-instrumented-files-and-not-files-in-memory"></a>

* Check your configuration is not using a In-Memory server (e.g. Webpack's server) and serves to your browser client the static files instrumented
* You can try a simple http server like [httpster ](https://www.npmjs.com/package/httpster)for a quick validation via a command similar to `httpster -p 8080 -d /home/somedir/public_html`

\ <br>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.sealights.io/knowledgebase/setup-and-configuration/troubleshooting-faq/node-javascript/js-no-front-end-coverage.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.