Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Object doesn't support property or method 'repeat' #1771

Closed
zxlin opened this issue Oct 6, 2020 · 2 comments · Fixed by #1772
Closed

Object doesn't support property or method 'repeat' #1771

zxlin opened this issue Oct 6, 2020 · 2 comments · Fixed by #1772
Labels
L1 - broken Valid usage causes incorrect output OR a crash AND there is no known workaround for the issue released

Comments

@zxlin
Copy link

zxlin commented Oct 6, 2020

Describe the bug

I got the following error message:

Object doesn't support property or method 'repeat' Please report this to https://github.com/markedjs/marked.

Below is the stack trace on the offending line, looks like it's the 'a'.repeat call.

Screen Shot 2020-10-06 at 2 17 28 AM

{
description: Object doesn't support property or method 'repeat', 
message: 
Object doesn't support property or method 'repeat'
Please report this to https://github.com/markedjs/marked.
, 
name: TypeError, 
number: -2146827850, 
stack: 
TypeError: Object doesn't support property or method 'repeat'
Please report this to https://github.com/markedjs/marked.
   at n.inlineTokens (https://cloudfront.net/3902fca11e4d36519d64b2e912f584b6349ba96e/js/webpack.commons.js?t=4:430:121356)
   at n.inline (https://cloudfront.net/3902fca11e4d36519d64b2e912f584b6349ba96e/js/webpack.commons.js?t=4:430:120374)
   at n.lex (https://cloudfront.net/3902fca11e4d36519d64b2e912f584b6349ba96e/js/webpack.commons.js?t=4:430:118496)
   at e.lex (https://cloudfront.net/3902fca11e4d36519d64b2e912f584b6349ba96e/js/webpack.commons.js?t=4:430:118370)
   at fe (https://cloudfront.net/3902fca11e4d36519d64b2e912f584b6349ba96e/js/webpack.commons.js?t=4:430:129607)
   at L (https://cloudfront.net/3902fca11e4d36519d64b2e912f584b6349ba96e/js/webpack.commons.js?t=4:32:196047)
   at Vi (https://cloudfront.net/3902fca11e4d36519d64b2e912f584b6349ba96e/js/webpack.commons.js?t=4:459:52928)
   at Oo (https://cloudfront.net/3902fca11e4d36519d64b2e912f584b6349ba96e/js/webpack.commons.js?t=4:459:65223)
   at Ha (https://cloudfront.net/3902fca11e4d36519d64b2e912f584b6349ba96e/js/webpack.commons.js?t=4:459:90397)
   at Ya (https://cloudfront.net/3902fca11e4d36519d64b2e912f584b6349ba96e/js/webpack.commons.js?t=4:459:90784)
   at Es (https://cloudfront.net/3902fca11e4d36519d64b2e912f584b6349ba96e/js/webpack.commons.js?t=4:459:97813)
   at Ss (https://cloudfront.net/3902fca11e4d36519d64b2e912f584b6349ba96e/js/webpack.commons.js?t=4:459:97193)
   at bs (https://cloudfront.net/3902fca11e4d36519d64b2e912f584b6349ba96e/js/webpack.commons.js?t=4:459:96214)
   at qa (https://cloudfront.net/3902fca11e4d36519d64b2e912f584b6349ba96e/js/webpack.commons.js?t=4:459:95083)
   at ui.enqueueSetState (https://cloudfront.net/3902fca11e4d36519d64b2e912f584b6349ba96e/js/webpack.commons.js?t=4:459:44749)
   at k.prototype.setState (https://cloudfront.net/3902fca11e4d36519d64b2e912f584b6349ba96e/js/webpack.commons.js?t=4:467:1657)
   at o (https://cloudfront.net/3902fca11e4d36519d64b2e912f584b6349ba96e/js/webpack.commons.js?t=4:27:2826)
   at c.prototype.emit (https://cloudfront.net/3902fca11e4d36519d64b2e912f584b6349ba96e/js/webpack.commons.js?t=4:422:18974)
   at value (https://cloudfront.net/3902fca11e4d36519d64b2e912f584b6349ba96e/js/webpack.commons.js?t=4:32:132805)
   at Anonymous function (https://cloudfront.net/3902fca11e4d36519d64b2e912f584b6349ba96e/js/webpack.commons.js?t=4:32:133785)
   at Anonymous function (https://cloudfront.net/3902fca11e4d36519d64b2e912f584b6349ba96e/js/webpack.commons.js?t=4:152:31009)
   at r (https://cloudfront.net/3902fca11e4d36519d64b2e912f584b6349ba96e/js/webpack.commons.js?t=4:476:15104)
}

To Reproduce

Windows 10, IE 11.0

Expected behavior

No errors to be thrown.

This looks like it's just an IE11 problem due to the lack of polyfill, not sure if the lib wants to address it or the polyfill is the problem of the user. I'm fine either way, but the message explicitly stated to report this, so here I am :)

@UziTech UziTech added the L1 - broken Valid usage causes incorrect output OR a crash AND there is no known workaround for the issue label Oct 6, 2020
@UziTech
Copy link
Member

UziTech commented Oct 6, 2020

Thanks for reporting this. We are trying to continue to support IE11. We will hopefully get a fix out soon.

@github-actions
Copy link

🎉 This issue has been resolved in version 1.2.2 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
L1 - broken Valid usage causes incorrect output OR a crash AND there is no known workaround for the issue released
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants