Skip to content

/standard

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

Question: browser objects #672

Closed
charliewilco opened this issue Nov 2, 2016 · 1 comment

Comments

@charliewilco
Copy link

commented Nov 2, 2016

screenshot 2016-11-02 00 33 09

any ideas how to not get this error? HTMLElement is apart of the window object but if i use the import statement webpack can't resolve it. (originally i was thinking webpack would resolve it like path in node or something similar)

@charliewilco charliewilco changed the title Question Question: browser objects Nov 2, 2016

@dcousens

This comment has been minimized.

Sign in to view
Copy link
Member

commented Nov 2, 2016 •
edited

https://github.com/feross/standard#how-do-i-hide-a-certain-warning

For this case, you could do

/* global HTMLElement */

But honestly, just use window.HTMLElement and avoid the ambiguity.

@dcousens dcousens closed this Nov 2, 2016

@dcousens dcousens added the question label Nov 2, 2016

@feross feross referenced this issue Jan 13, 2017
Closed

@lock lock bot locked as resolved and limited conversation to collaborators May 10, 2018

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
question
Milestone
No milestone
2 participants
@charliewilco @dcousens
You can’t perform that action at this time.