rt，带上了soucemap，但是目录是相对路径的。webpack无法直接识别，会一直报错

sourceMappingURL=assets-retry.umd.js.map

导致所有 background-image 都会带上 important，theme 场景下需要复写的话就要增加 css 权重，当时这个考虑是为了兼容 IE9？

When using this library, I had a problem: I already had retry logic for some of the resources, such as the important js resources, how I avoid retrying these resources, I don't know the exact url of these resources, using the following function is not a good idea:

// onRetry hook is how you can customize retry logic with, default is x => x
onRetry: function(currentUrl, originalUrl, statistics) {
// Here is a judgment. It seems unfriendly to my situation
if(currentUrl.indexOf('xxx') > -1){
return null;
}
return currentUrl
},

I am thinking add a custom attribute to the html tag to control retry，e.g. when creating html tags, add an attribute data-assets-retry-ignore to <script> tag, then the resources with the special attribute will not retry to load by this library, even if it fails. I am looking forward to the library support retries that ignore certain specified resources.

Thanks~

☝️ Important announcement: Greenkeeper will be saying goodbye 👋 and passing the torch to Snyk on June 3rd, 2020! Find out how to migrate to Snyk and more at greenkeeper.io

The devDependency @types/node was updated from 13.9.2 to 13.9.3.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@types/node is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

The devDependency lint-staged was updated from 10.0.7 to 10.0.8.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

lint-staged is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

I'm submitting a...

[ ] Regression 
[ ] Bug report
[x] Feature request
[ ] Documentation issue or request
[ ] Support request

Current behavior

当上一个资源重试后，会永久性的改变使用的 domain，导致下一个资源也是使用该 domain.

Expected behavior

每次加载新的资源都重置使用的 domain，从第一个 domain 开始加载，不然可能 cdn 只是少了一个文件，导致后面的资源都用不了该 cdn 地址。

What is the motivation / use case for changing the behavior?

可能 cdn 只是少了一个文件，导致后面的资源都用不了该 cdn 地址。

Environment

Assets-retry version: 0.3.2

下面这里不是很明白，如下script的的写法执行顺序是串行同步的，app.js 加载出错的情况下，vendor已经是加载完了，而且，document.createElement 只是创建一个script标签而已，在还是loading的状态下，依旧这样处理会有什么问题？

I'm submitting a...

[ ] Regression 
[✅] Bug report
[ ] Feature request
[ ] Documentation issue or request
[ ] Support request

Current behavior

当js链接使用link标签进行preload预加载后，只retry了预加载的link标签，而对同一个url的js的script标签没有进行retry，导致js没有重试执行
css链接同样的问题

Expected behavior

不仅preload的资源retry，同一个url的script或者style标签也能正确retry

Minimal reproduction of the problem with instructions

What is the motivation / use case for changing the behavior?

Environment

Assets-retry version: 0.3.4

 
For Tooling issues:
- Browser version: Google Chrome Version 112.0.5615.137 (Official Build) (arm64)
- Platform:   Mac M1

Others:

dist里没有声明文件，搞个typing吧

The devDependency rollup was updated from 1.31.0 to 1.31.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

rollup is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

add support images defined in inline style tags

<style>
	.img {
		background-image: url('//your.cdn/path/to/image')
	}
</style>

Hello I wanna know is this lib can confirm the scripts with defer attribute will works the same as browser default behavior ?

• origin with order

1. cdn1/a.js (200)
2. cdn1/b.js (403)
3. cdn1/c.js (200)

• expected browser excecution order

1. cdn1/a.js (200)
2. cdn1/b.js (403) -> 3. cdn2.b.js
3. cdn1/c.js (200)

☝️ Important announcement: Greenkeeper will be saying goodbye 👋 and passing the torch to Snyk on June 3rd, 2020! Find out how to migrate to Snyk and more at greenkeeper.io

The devDependency lint-staged was updated from 10.0.8 to 10.0.9.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

lint-staged is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

请问下，在 retry-async 中的 createHookedElement 是返回了一个新构造的代理对象 $hookedElement：

为此，还需要 hack Node 和 Element （hookPrototype） 来识别新的对象；

另一种做法是在源对象上代理 onload，onerror 和 addEventListener，这样似乎就不需要 hack Node 和 Element 了。

采用返回新对象的方式有什么特别的考虑吗？

没太懂这里的方式是做啥？

hookCreateElement(opts) 已经修改了document.createElement的方法，出错的时候就可以重试了呀。

下面这两个方法是在干嘛？

 target[key] = function(): any {
            const args = [].slice.call(arguments).map((item: any) => {
                if (!item) return item;
                return hasOwn.call(item, innerScriptProp) ? item[innerScriptProp] : item
            })
            return originalFunc.apply(this, args)
        }
        // keep original toString
        if (/^\w+$/.test(key)) {
            target[key].toString = new Function(`return 'function ${key}() { [native code] }'`)
        }

The devDependency @typescript-eslint/eslint-plugin-tslint was updated from 2.18.0 to 2.19.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@typescript-eslint/eslint-plugin-tslint is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

☝️ Important announcement: Greenkeeper will be saying goodbye 👋 and passing the torch to Snyk on June 3rd, 2020! Find out how to migrate to Snyk and more at greenkeeper.io

The devDependency cross-env was updated from 7.0.1 to 7.0.2.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

cross-env is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

The devDependency typedoc was updated from 0.15.3 to 0.15.4.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

typedoc is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

I'm submitting a...

[ ] Regression 
[x] Bug report
[ ] Feature request
[ ] Documentation issue or request
[ ] Support request

Current behavior

异步脚本加载超时没有触发重试机制。

Expected behavior

当异步脚本加载超时也能触发重试机制。

Minimal reproduction of the problem with instructions

使用 whistle 延迟脚本加载时长。

xxx reqDelay://180000

FYI: https://wproxy.org/whistle/rules/reqDelay.html

What is the motivation / use case for changing the behavior?

Environment

Assets-retry version: 0.3.3

 
For Tooling issues:
- Browser version: Chrome 105.0.5195.125
- Platform:  Mac

Others:

☝️ Important announcement: Greenkeeper will be saying goodbye 👋 and passing the torch to Snyk on June 3rd, 2020! Find out how to migrate to Snyk and more at greenkeeper.io

The devDependency @typescript-eslint/parser was updated from 2.24.0 to 2.25.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@typescript-eslint/parser is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

I'm submitting a...

[ ] Regression 
[x] Bug report
[ ] Feature request
[ ] Documentation issue or request
[ ] Support request

Current behavior

hookElement 出来的不是 Node，导致 appendChild 的时候出错。

{
  "message":"Failed to execute 'appendChild' on 'Node': parameter 1 is not of type 'Node'.",
  "name":"TypeError",
  "stack":"TypeError: Failed to execute 'appendChild' on 'Node': parameter 1 is not of type 'Node'.\n"
}

Expected behavior

能确保 hookElement 出来的一定是 Node.

Minimal reproduction of the problem with instructions

偶现情况，暂未找到原因

What is the motivation / use case for changing the behavior?

不会阻塞其他脚本的加载

Environment

Assets-retry version: 0.3.3

 
For Tooling issues:
- Browser version: Edge(103.0)
- Platform:  Windows

Others:
- userAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/103.0.5060.53 Safari/537.36 Edg/103.0.1264.37

The devDependency rollup was updated from 1.27.8 to 1.27.9.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

rollup is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

讨论：CSS 背景图采用拼接多个 url 方案会导致浏览器额外多出资源请求

[ ] Regression 
[x] Bug report
[ ] Feature request
[ ] Documentation issue or request
[ ] Support request

Current behavior

CSS 背景图采用拼接多个 url 方案会导致浏览器额外多出资源请求，在实际大规模业务使用中这部分方案应该是有问题的

Expected behavior

目前思考思路：
1、通过 serviceworker 进行拦截请求处理
2、通过 performance 监听，判断可能为异常再 insertRule （移除当前的 setInterval）

I'm submitting a...

[ ] Regression 
[ ] Bug report
[ ] Feature request
[ ] Documentation issue or request
[ ] Support request
[x ] confusion

同步资源的加载监听核心是通过如下代码实现的
document.addEventListener('error', errorHandler, true) document.addEventListener('load', loadHandler, true)
想请教的是，这里的监听回调函数是会被同步触发的么？我认知里理解的这些回调函数都是异步触发的，如果是异步触发的，js script 加载异常的场景下，怎么能保证及时拦截并重试加载呢？

@Nikaple 求大佬帮忙解惑，感激不尽。

The devDependency @typescript-eslint/eslint-plugin was updated from 2.19.0 to 2.19.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@typescript-eslint/eslint-plugin is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

在 src/retry-sync.ts 中没有判断 event 对象是不是由于网络错误导致的 error，那么 script 标签本身执行报错了是不是也会触发这个函数呢？

☝️ Important announcement: Greenkeeper will be saying goodbye 👋 and passing the torch to Snyk on June 3rd, 2020! Find out how to migrate to Snyk and more at greenkeeper.io

The devDependency @typescript-eslint/eslint-plugin-tslint was updated from 2.24.0 to 2.25.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@typescript-eslint/eslint-plugin-tslint is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

domain：

背景图：

重试：

类似 new Function(return 'function ${key}() { [native code] }')的代码
会引起
1: csp严格模式下会有问题
2: 改写原生属性上的方法时，业务中再次调用方法会出现问题，如下图

The devDependency @types/node was updated from 12.12.14 to 12.12.15.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@types/node is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

The devDependency @typescript-eslint/parser was updated from 2.19.0 to 2.19.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@typescript-eslint/parser is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

引入到项目中以后发现一个问题，如上图，css的加载也有resolve和reject的处理，会导致项目报错，这个是不是也要和js一样做async的处理？

我的应用代码是这样的

window.assetsRetryStatistics = window.assetsRetry({
    domain: ['cdn.a.com', 'cdn.b.com'],
    maxRetryCount: 1
})

css中的background-image会自动添加备用域名cdn.b.com域名的url

.normal-module_contentLessonsPracticeNothing_2H-mB::before {
    background-image: url(http://cdn.a.com/img/no-task.7e4726d6.png), 
        url(http://cdn.b.com/img/no-task.7e4726d6.png) !important;
}

这样浏览器会向这两个资源都发起请求，请问这样是否符合css背景图片重试的预期。
谢谢！

The devDependency eslint-plugin-import was updated from 2.18.2 to 2.19.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

eslint-plugin-import is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

The devDependency typedoc was updated from 0.16.10 to 0.16.11.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

typedoc is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

The devDependency @types/node was updated from 13.7.0 to 13.7.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@types/node is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

在vue单页项目或者单个页面有多个相同资源请求的情况下，retryTimes超过maxRetryCount时被视为fail，导致资源不会重试。

<img src="http://cdn.a.com/img/1.png">
<img src="http://cdn.a.com/img/1.png">
<img src="http://cdn.a.com/img/1.png">

在单页应用中，在路由来回切换过程中 currentCollector['/img/1.png']的retryTimes属性会累加，导致超过maxRetryCount，然后之后的/img/1.png不会被重试

一、这里没太看明白，我在项目中模拟动态加载

一样是可以被 document.addEventListener('error', errorHandler, true) 捕获的到啊，不用动态的也可以重试

  // 模拟动态加载js报错
    function test() {
        var chunk
        new Promise(function (resolve, reject) {
            chunk = [resolve, reject];
        });

        const scriptVal = document.createElement('script');
        scriptVal.src = 'https://www.test.com/ajax/libs/jquery/3.5.1/jquery.js';

        scriptVal.onerror = chunk[1](new Error('加载报错'))

        document.body.appendChild(scriptVal);

    }
    document.getElementById('test').addEventListener('click', test);

In src/util.ts, I found doc.write() is only used when the browser is not IE or Edge.

In IE or Edge, the library appends script to head element, the loading order may be wrong?

The devDependency rimraf was updated from 3.0.1 to 3.0.2.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

rimraf is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

超级赞👍的代码，这两天正好在做这块
我在document.stylesheets时
uncaught DOMException: Failed to read the 'rules' property from 'CSSStyleSheet': Cannot access rules
at HTMLDocument.

是您在文档常见问题里说的那个问题么。
在实际应用时是不是会经常出现读不到CSSStyleSheet的情况，就不能正常retrycss，处理背景图这样的问题。

The devDependency selenium-webdriver was updated from 4.0.0-alpha.5 to 4.0.0-alpha.6.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

selenium-webdriver is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

The devDependency @rollup/plugin-json was updated from 4.0.1 to 4.0.2.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@rollup/plugin-json is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

I'm submitting a...

[ ] Regression 
[x] Bug report
[ ] Feature request
[ ] Documentation issue or request
[ ] Support request

Current behavior

使用 js 动态添加/移除 style 标签
style 标签会变成 Detached Element 无法被 GC 造成内存泄漏

使用 Edge 的 Detached Elements 分析，调用 removeChild 将 style 移除后，style 标签变成 Detached Element

Expected behavior

style 标签被 remove 后可以被正确 GC

Minimal reproduction of the problem with instructions

执行以下代码

    let styleElement: any = document.createElement('style')
    document.body.appendChild(styleElement)
    setTimeout(() => {
      document.body.removeChild(styleElement)
      styleElement = undefined
    }, 1000)

可以使用 Edge 浏览器的 Detached Elements 确认

What is the motivation / use case for changing the behavior?

Environment

Assets-retry version: 0.3.3

 
For Tooling issues:
- Browser version: Microsoft Edge 107.0.1418.24  
- Platform:  Mac

Others:

查看源码发现 retry-css.ts 中， handledStylesheets 缓存了 style 标签的引用，当 style 标签移除时，没有清理这里的缓存，这里还保留引用导致无法被 GC

I'm submitting a...

[ ] Regression 
[ ] Bug report
[ ] Feature request
[ ] Documentation issue or request
[ ] Support request

Current behavior

html内存在多个带defer的<script>，而且必须按顺序执行，若只挂了第一个script，retry插入的<script>执行顺序不正确。我清楚问题原因，但是没有好的方案。有什么好的解决办法吗？

Expected behavior

Minimal reproduction of the problem with instructions

What is the motivation / use case for changing the behavior?

Environment

Assets-retry version: X.Y.Z

 
For Tooling issues:
- Browser version: XX 
- Platform:  

Others: