# @soda/get-current-script

> get the current executing script, with polyfills for IE9+ and Firefox

Latest version **1.0.2** (published 2020-06-16) · MIT license · 0 weekly downloads

## Install

```sh
npm install @soda/get-current-script
pnpm add @soda/get-current-script
yarn add @soda/get-current-script
bun add @soda/get-current-script
```

## Health

**Score 15/100 (F)** — status: abandoned.

Positive: no vulnerabilities.

Warnings: low downloads; no types; no esm support.

Negative: abandoned; low maintenance score.

## Facts

| | |
|---|---|
| Version | 1.0.2 |
| Published | 2020-06-16 |
| First published | 2020-03-09 |
| Weekly downloads | 0 |
| License | MIT |
| TypeScript types | none |
| Module format | CommonJS |
| Dependencies | 0 |
| Unpacked size | 14.2 KB |
| Known vulnerabilities | 0 |
| Install scripts | no |
| GitHub stars | 12 |
| Author | Haoqun Jiang |
| Maintainers | soda |

## Links

- npm: https://www.npmjs.com/package/@soda/get-current-script
- Repository: https://github.com/sodatea/get-current-script
- Homepage: https://github.com/sodatea/get-current-script#readme
- Issues: https://github.com/sodatea/get-current-script/issues
- npm.io page: https://npm.io/package/@soda/get-current-script

## Recent versions

- 1.0.2 (latest) — 2020-06-16
- 1.0.1 — 2020-06-04
- 1.0.0 — 2020-03-09

## README

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

---
_Source: https://npm.io/package/@soda/get-current-script · Machine-readable twin of the npm.io package page. Health data is recomputed on every publish._