WorkerGlobalScope: importScripts() method
Note: This feature is only available in Web Workers.
The importScripts()
method of the WorkerGlobalScope
interface synchronously imports one or more scripts into the worker's scope.
Syntax
importScripts(path0)
importScripts(path0, path1)
importScripts(path0, path1, /* …, */ pathN)
Parameters
pathN
-
A string value representing the URL of the script to be imported. The URL may be absolute or relative. If the URL is relative, it is relative to the worker entry script's URL.
Return value
None (undefined
).
Exceptions
NetworkError
-
Imported scripts were served without a
text/javascript
MIME type or without one of the permitted legacy JavaScript MIME types. TypeError
-
Thrown if the current
WorkerGlobalScope
is a module. Useimport
instead.
Examples
If you had some functionality written in a separate script called foo.js
that you wanted to use inside worker.js
, you could import it using the following line:
importScripts("foo.js");
foo.js
should be in the same URL subtree as the worker's entry point — for example, if this worker was created with new Worker("worker.js")
, then worker.js
is the entry point. If worker.js
is at https://example.com/scripts/worker.js
, then foo.js
should be at https://example.com/scripts/foo.js
.
importScripts()
and self.importScripts()
are effectively equivalent — both represent importScripts()
being called from inside the worker's inner scope.
Specifications
Specification |
---|
HTML Standard # dom-workerglobalscope-importscripts-dev |
Browser compatibility
BCD tables only load in the browser