Assertion: script | /r/HasProperty | run
Facets:
value: from the root of the module
type: OTHER
value: within
type: DEGREE
value: regardless of
type: OTHER
value: -interactively
type: MANNER
value: from within the script editor application
type: LOCATION
value: as quickly as
type: MANNER
Source sentences:
text: From a technical standpoint, most modern JavaScript interpreters actually use a technique called just-in-time compiling to improve performance; the JavaScript source code gets compiled into a faster, binary format while the script is being used, so that it can be run as quickly as possible.
text: Run handler Defines the main code of the script, which is called when the script is run.
text: You could even omit that line if you wanted to run the script by sourcing it at the shell, but let’s save ourselves some trouble and add it to allow scripts to be run non-interactively.
text: Which in this case is entered the first time the script is run.
text: The engine must re-obtain these pointers after the script is run again.
text: Scripts can be “run” from within the Script Editor application or saved as either script files or script applications, available for use at any time, and from within any application.
text: The actual shell your script is run within is platform dependent.
text: Scripts are run from the root of the module, regardless of what your current working directory is when you call npm run .
text: Simple deployment approach: just bring both the script and engine files (about 30 K size) on a system that has the .NET runtime installed, and the script can be run
text: document_start string Scripts are injected after any files from css , but before any other DOM is constructed or any other script is run.
text: Listing a script in dependencies doesn't cause that script to be run; it still has to be selected through the --script option or otherwise.
text: A script must contain one or more of the following functions that determine when the script will be run: prerule() hostrule(host)