New issue
Advanced search Search tips

Issue 766188 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner:
Closed: Oct 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

es6 modules problem

Reported by fsx950...@gmail.com, Sep 18 2017

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.91 Safari/537.36

Steps to reproduce the problem:
1. npm install material-components-web 
2. import {MDCToolbar} from 'node_modules/@material/toolbar/index.js';
3. run web page

What is the expected behavior?
import success

What went wrong?
es6 import doesn't work well with mdc

Did this work before? No 

Chrome version: 61.0.3163.91  Channel: stable
OS Version: 10.0
Flash Version:
 

Comment 1 by fsx950...@gmail.com, Sep 18 2017

There are screenshoots
屏幕截图(11).png
131 KB View Download
屏幕截图(12).png
152 KB View Download
Labels: Needs-Triage-M61
Components: -Blink Blink>JavaScript
Cc: pbomm...@chromium.org
Labels: TE-NeedsTriageHelp
Tagging with Triage help label as this require dev team help.
Cc: adamk@chromium.org
Components: -Blink>JavaScript Blink>JavaScript>Language
Status: Available (was: Unconfirmed)

Comment 7 by adamk@chromium.org, Oct 3 2017

Owner: adamk@chromium.org
Status: WontFix (was: Available)
This is working as intended. In the browser, imported module specifiers must be URL-like (and are resolved as URLs). The example module here tries to import from "@material/base", which is invalid per the HTML spec.
There are a lot of packages use import in this way.How to compatible them

2017年10月4日 上午4:59,"ad… via monorail" <monorail+v2.3002369578@chromium.org

Sign in to add a comment