Name	Last modified	Size	Description
	Parent Directory		-
	fixtures/	2023-06-08 13:45	-
	nightwatch.conf.js	2023-06-08 13:45	4.7K	0fb859dc fixed mobile overflwo options [كارل مبارك]
	index.js	2023-06-08 13:45	2.8K	0fb859dc fixed mobile overflwo options [كارل مبارك]
	package.json	2023-06-08 13:45	2.2K	0fb859dc fixed mobile overflwo options [كارل مبارك]
	README.md	2023-06-08 13:45	1.2K	0fb859dc fixed mobile overflwo options [كارل مبارك]
	LICENSE	2023-06-08 13:45	1.1K	0fb859dc fixed mobile overflwo options [كارل مبارك]
	test.js	2023-06-08 13:45	733	0fb859dc fixed mobile overflwo options [كارل مبارك]

# @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
```