Parsing error when "new Crawler()" is not called on line 1 of the crawler editor

[timngyn]

Description

When new Crawler({...}) is not on line 1 of the editor, there is a configuration error saying Crawler is not defined. Should this be happening?

In this picture, if I remove the new line above new Crawler(...) then the parsing error goes away.

Some background:

• Our site is part of the docsearch program and I am trying to define a variable to be used in my crawler action objects for the pathsToMatch property. For some of our URLs, the records getting returned are too large and so we want to have a separate action for these URLs, as shown in this github issue comment: Extractors returned too many records #1658 (comment)
• We have around 29 urls and so I wanted to define this as an array above the instantiation for the new Crawler and use the variable in pathsToMatch like in the above issue comment

Steps to reproduce

1. Go to the Algolia crawler editor
2. In the editor, add a new line above new Crawler({...})
3. Observe that the Configuration Error tab appears on the right side, saying that there is a parsing error and that Crawler is not defined

Expected behavior

Since the editor is for editing the script, I would expect there to be no parsing error based on where the new Crawler is defined.

Environment

• OS: Mac
• Browser: Chrome
• DocSearch version: 3.0.0