5380aef78b9fd0085eeb7b619a4e6b8b58c1af684e3349f77af1ec902c2015d597b8d312026e8633b4fc2171a95c7e15c8b183efeb34c3e88a389f9b63b687 1.2 KB

1234567891011121314151617181920
  1. # @soda/get-current-script ![CI](https://github.com/sodatea/get-current-script/workflows/CI/badge.svg)
  2. It is basically a function that returns `document.currentScript` but with support for IE9-11, thanks to https://github.com/amiller-gh/currentScript-polyfill.
  3. 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.
  4. 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.
  5. 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!
  6. ## Usage
  7. ```sh
  8. npm i @soda/get-current-script
  9. ```
  10. ```js
  11. const getCurrentScript = require('@soda/get-current-script')
  12. const script = getCurrentScript() // the current executing <script> element
  13. ```