Excluding Inline JS from combine
If this behavior is creating any issue on your site, you can exclude inline JS from the combine option.
In this Article
Exclude specific scripts
If you're experiencing an issue with too many JS files being created, please read this guide:
Fix Large Cache Folder Size Caused by Dynamic Inline JS
Exclude all inline scripts
It can be useful to quickly exclude all inline scripts while troubleshooting, to check if the issue you're facing is related to inline scripts at all. To exclude them all, add the following in the exclusion field:
How to find inline JS to exclude
The instructions below will cover cases where the optimization of Inline JS is causing an error message in your browser console.
We understand it can be difficult to locate which inline JS to exclude, so we'll walk through one way to do it.
In this example, we refer specifically to using the Chrome browser.
Open Developer Tools. You do that either by right-clicking and choosing Inspect Element, or at the top of the window go to: View→Developer→Developer Tools
Find the red error message indicator on the right-hand side:
Click it to open the Console, then click the file referenced in the error notice:
This takes you directly to the code in the file that is related to the error. Look for the red underline and copy part of that code:
Open a new browser tab and load the uncached version of the page. You do that by adding ?nowprocket to the URL—this will load an uncached, unminified version of the page. It is necessary in order to find the original URLs of the files.
An uncached URL would look something like:
Open Developer Tools in the new browser, then click on the Console:
Paste the following code in the Console:(snippet found here)
Press enter to populate the console with all scripts, including inline scripts in red:
If the error is related to a 3rd party JS file, follow the directions here to exclude it from combining.