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

IE 11, bug #24

Closed
andalt opened this issue Dec 26, 2017 · 8 comments
Closed

IE 11, bug #24

andalt opened this issue Dec 26, 2017 · 8 comments

Comments

@andalt
Copy link

andalt commented Dec 26, 2017

http://joxi.ru/8An0lpqTqenMOm
http://joxi.ru/n2YzJZxUj8nKOA

@uNmAnNeR
Copy link
Owner

Please, provide some description and steps to reproduce.

@ramlmn
Copy link

ramlmn commented Dec 26, 2017

This is not a problem with the library. You are using default function params on line 1132, an ES6 feature which doesn't work in Edge < 14.

I see you are using Webpack, but not transpiling. If you are transpiling, then let me know about your Babel config.

@uNmAnNeR
Copy link
Owner

@ramlmn @andalt the line 1132 is from imask.
Probably webpack take es version of imask and does not transpile it properly.
@ramlmn thank you! if you could help, please kindly help him. I dont have time for that kind of issues.

@andalt
Copy link
Author

andalt commented Dec 26, 2017

@ramlmn @uNmAnNeR Thank you very much for the answers. You are right.
config -
module: {
rules: [{
test: /.js$/,
exclude: [/(node_modules)/],
loader: 'babel-loader',
options: {
presets: [
['env', {
targets: {
['last 2 versions', 'ie 11']
}
}]
]
}
}]
}

babelrc -
{
"presets": ["env"]
}

@uNmAnNeR
Copy link
Owner

in short there is a problem in line
exclude: [/(node_modules)/],
which also excludes imask from transpiling.

Use appropriate regexp to avoid excluding imask from node_modules.
This and that could help.

@andalt
Copy link
Author

andalt commented Dec 26, 2017

@uNmAnNeR Thank you!
exclude: /node_modules(?!(/|\)imask)/, - worked

@uNmAnNeR
Copy link
Owner

nice

@ramlmn
Copy link

ramlmn commented Dec 26, 2017

Glad the problem got solved!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants