You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 18, 2024. It is now read-only.
I believe that material-components-web is written in a ES2015 module style which causes lots of issues when I tried to include it in a new jspm / system.js based website.
lots of errors logged in the .jspm-errors files.
"Unexpected reserved word export"
"Unexpected reserved word import"
etc
The text was updated successfully, but these errors were encountered:
Do I need to flag these modules as being 'esm' format?
meta: {
'@material/*': {
format: 'esm'
}
}
I will try this tonight... maybe this will give system.js the information it needs.
I am thinking I need to transpile on the browser while in development but transpile and bundle for production. Does that sound about right?
It should just work out of the box if you're using transpiler: 'plugin-babel' or transpiler: 'plugin-traceur' or transpiler: 'plugin-typescript', what version of jspm are you using?
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I believe that material-components-web is written in a ES2015 module style which causes lots of issues when I tried to include it in a new jspm / system.js based website.
lots of errors logged in the .jspm-errors files.
"Unexpected reserved word export"
"Unexpected reserved word import"
etc
The text was updated successfully, but these errors were encountered: