MDCTopAppBar README should not import index file
See original GitHub issueIn the MDCTopAppBar README here.
The import statement should not import the /index
but rather the package name.
// From
import {MDCTextField} from '@material/textfield/index';
// To
import {MDCTextField} from '@material/textfield';
As per the importing-js.md and #4509
Issue Analytics
- State:
- Created 4 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
Github pages is showing my ReadMe file not the html file?
Not seeing any index.html file in your github. If todolist.html is the one refering to, maybe try renaming it to index.html. That should...
Read more >Project Settings - ReadMe Documentation
Avoid importing versions that already exist in ReadMe. It's important to note that if there are clashing versions between those existing in ReadMe...
Read more >Nimib Docs - GitHub Pages
It currently does not provide any type of interactivity or automatic reloading ... though nimib both as an index.html file and as a...
Read more >@angular-mdc/web: Versions | Openbase
ripple: Fix mdcRipple directive not working; menu-surface: Add Ivy compatible directive decorator; select: Should not emit touch event until menu closes; select ...
Read more >9.5 Setting up a project in RStudio - An Introduction to R
You should now see the README.md file listed in your repository. It won't actually exist on your computer yet as you will need...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
That comment is similarly obsolete for the same reason. It was written before we were able to define the
module
property inpackage.json
(because prior to the TypeScript conversion, our ES modules’ contents were not purely ES5).@kfranqueiro Oh. I see.