f5e6e29f00
# Conflicts: # jsowell-ui/.env.development # jsowell-ui/.env.staging # jsowell-ui/bin/build-sit.bat # jsowell-ui/bin/build.bat # jsowell-ui/src/api/adapayMember/adapayMember.js # jsowell-ui/src/api/pile/merchant.js # jsowell-ui/src/router/index.js # jsowell-ui/src/views/financial/financeDetail.vue # jsowell-ui/src/views/financial/merchant.vue # jsowell-ui/src/views/homeIndex/homeIndex.vue # jsowell-ui/src/views/login.vue # jsowell-ui/src/views/pile/basic/detail.vue # jsowell-ui/src/views/pile/station/components/SiteInfo.vue # jsowell-ui/src/views/pile/station/detail.vue # jsowell-ui/src/views/pile/station/orderReport.vue
@soda/get-current-script 
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 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
npm i @soda/get-current-script
const getCurrentScript = require('@soda/get-current-script')
const script = getCurrentScript() // the current executing <script> element