webdav/sync/jcore/web/front_end/node_modules/@soda/get-current-script - 志元云盘

File OriginalPic	EditTime	Size
fixtures	2024-07-22 14:00:56	1.42 KB
index.js	2024-07-14 16:16:53	2.8 KB
LICENSE	2024-07-14 16:16:54	1.08 KB
nightwatch.conf.js	2024-07-14 16:16:53	4.66 KB
package.json	2024-07-14 16:16:54	2.13 KB
README.md	2024-07-14 16:16:53	1.19 KB
test.js	2024-07-14 16:16:53	733 B

# @soda/get-current-script ![CI](https://github.com/sodatea/get-current-script/workflows/CI/badge.svg)

It is basically a function that returns `document.currentScript` but with support for IE9-11, thanks to https://github.com/amiller-gh/currentScript-polyfill.

It also works around a [Firefox issue](https://bugzilla.mozilla.org/show_bug.cgi?id=1620505) when the script is called in a microtask, which makes `document.currentScript` unusable in a webpack dynamic-imported chunk.

It is shipped as a utility function rather than a polyfill, because we can't easily tell if the `document.currentScript` is returning `null` due to the Firefox issue or because it's running in an event handler / a callback.

The implementation here may not adhere strictly to `document.currentScript` spec when called in async code or in a callback. In these situations the spec calls for `document.currentScript` to return `null`. However, for the grand majority of your `document.currentScript` needs, this utility will do the job!

## Usage

```sh
npm i @soda/get-current-script
```

```js
const getCurrentScript = require('@soda/get-current-script')
const script = getCurrentScript() // the current executing <script> element
```

云盘

Home / 志元云盘 / webdav / sync / jcore / web / front_end / node_modules / @soda / get-current-script