-
Notifications
You must be signed in to change notification settings - Fork 224
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 webpack support #159
Fix webpack support #159
Conversation
Awesome, thank you! |
Hmm, seems like the tests are failing, any idea why? |
Unsure. Will try to look later tonight.
Re: the test versions, seems like 0.10 and 0.12 can be cut out and 4.x,
6.x, and latest should be the only things tested, no?
…On Mon, Nov 28, 2016 at 4:07 AM Linus Unnebäck ***@***.***> wrote:
Hmm, seems like the tests are failing, any idea why?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#159 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAL_Jv-Jp4l-ye4aX3gqbp-eIrGlXCeCks5rCqfogaJpZM4K9Tk4>
.
|
I don't think we should drop 0.10 or 0.12 support without cutting a major release... |
To be fair this is 0.x series so technically can do whatever you want, but
I get you. A 1.x would be nice :)
…On Mon, Nov 28, 2016 at 3:45 PM John-David Dalton ***@***.***> wrote:
Major bump 🎉
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#159 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAL_JnIY44LiTxg66tjCgugOlKMFV08iks5rC0uSgaJpZM4K9Tk4>
.
|
@LinusU as always, sorry for the delay. Two issues with the tests:
Both are fixed with the latest version of the PR. I have not changed anything WRT version, etc. |
if (!contents && fs.existsSync(source)) { | ||
contents = fs.readFileSync(source, 'utf8'); | ||
try { | ||
const fs = require('fs'); |
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.
This should probably be var
to not upset any old browsers? Maybe we can move the try
/catch
to the top of the file even 🤔
var fs
try {
fs = require('fs')
} catch (_) {
// Loading in catch block to convert webpack error to warning.
}
if (!contents && fs && fs.existsSync(source)) {
contents = fs.readFileSync(source, 'utf8');
This is amazing 😍 only one small nit, then it's good to go! |
@LinusU done. |
Thank you! |
Released as 0.4.9 |
This converts the webpack errors to warnings. Individual users may use the ignore plugin to further mute these warnings.