-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
[15.1] ie11 fails with syntax error at strip-ansi eval #1618
Comments
Can you please open the inspector in IE and paste the errors here? |
SCRIPT1002: Syntax error Here is lines 1552-1556: // "./node_modules/strip-ansi/index.js": "use strict"; |
I don't know if it is related to this but the language pack doesn't pass through babel (tested with selectedRows: rows => rows > 0 ? `${rows} row${rows === 1 ? '' : 's'} selected.` : 'No selected rows.', So the file is not transpiled and it is put directly into the vendor bundle. You can fix it with: extendWebpack(cfg) {
for (const rule of cfg.module.rules) {
if (rule.loader === 'babel-loader') {
rule.include.push(
path.resolve(__dirname, 'node_modules/quasar-framework/i18n')
)
}
}
} in the |
Just confirmed ie11 issue is not in dist build. This only occurs in the localhost:8080 dev mode. |
Fixed it in v0.15.2 (released already). |
Updated to 0.15.2 on starter-kit Sorry to say it still has the same error.... |
Pls redo your tests. Run a "quasar info". Make sure you are indeed using 0.15.2. I am 100% sure this issue reported here is fixed. |
Hi, Sorry if I'm doing something wrong (Still a beginner Vue/Quasar coder) , but this still seem to be an issue. I've cleared cache, tried another PC, confirmed IE is in edge mode, etc, etc. I'm stumped. Here are the steps I did to update and the quasar output.
I also tried a new starter-kit with ie11 support. Same issue. Thanks for your help! |
Can you show me your quasar.conf.js pls? Trying to figure out something. |
I'm adding Object.assign polyfill (as indicated in webpack-dev-server ticket) to the Quasar ie-compat package for CLI v0.15.4. That should fix this. I am buffed though as I cannot reproduce :/ |
Ok, update to 0.15.4 and make one more try. Should be fixed now. Thanks. |
0.15.4 did not fix the issue. Same error. Just a note, this is IE 11.0.96 on Windows 7 that is failing. IE Edge on Windows 10 works fine (maybe your testing on this?). I assume ie11 compatability is supposed to work on Win7 IE 11? I didn't make any manual changes to the quasar.conf.js file in the starter-kit test I made. Did you still need it? |
Ok, so investigated together with Lou-Der. Seems like a problem with webpack when the dev server is run on a Windows 7 machine and consumed by IE11. However, it is not a problem when the dev server is run on a linux/mac/win10 machine and consumed by a IE11 on a win7 machine. Will add this to the docs. Unfortunately, until webpack gets a fix we can't do anything. There's nothing wrong from Quasar's side that generates this error. |
Hi, I have still the same issue on the 0.15.4 too: // "./node_modules/strip-ansi/index.js": "use strict"; This is IE 11.248.16299.0 on Windows 10. Thanks for the help |
Can you please do a small test: |
|
I have the same issue on the 0.15.10 too. |
Hi, I have the same transpiling issues with ie11 on Windows 10 with dev-server (build works) Global packages Important local packages |
Hi, Please use Yarn instead of npm. Delete node_modules folder and install again with Yarn. This is a known issue on webpack + npm combination on Windows. For some reason npm does not gets the right dependency tree. |
hi, using yarn solved the problem for me :) |
White screen on startup.
Reproduced this on a clean init project,
From my limited searching skills, I think this is related to webpack/webpack-dev-server#1286
The text was updated successfully, but these errors were encountered: