-
Notifications
You must be signed in to change notification settings - Fork 784
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
fix: do not warn when using webpack #3777
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm hesitant to downgrade this. IMO we ought to consider using a different build tool. Is 0.10 maintained?
Perhaps an issue should be created in the |
@@ -1082,12 +1082,14 @@ describe('color.getBackgroundColor', function () { | |||
it('returns the html background', function () { | |||
fixture.innerHTML = '<div id="target"><label>elm<input></label></div>'; | |||
document.documentElement.style.background = '#0F0'; | |||
document.body.setAttribute('style', 'background: unset'); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems Mocha added default styles to body
in a recent update, one of which was a white background and black foreground. So needed to unset the background color for the test.
Following the steps in the ticket, this fixes the webpack output to not warn of the critical dependency. Seems something about esbuild v0.11+ causes the problem. For now this is a fix to the problem, but I'll investigate further at some later date to see if I can figure out what's going on.
Closes issue: #3771