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 #114: webpack bundling #124
Fix #114: webpack bundling #124
Conversation
Looks really good 👍 Thank you 😄 |
Fix #114: webpack bundling
Hi, had the same problem with webpack. The PR above fixed the webpack builds for me. Do you plan to make a release with this fix in the near future? Thx, |
I can do it 😉 |
Thanks, would save me a lot of time trying to get around the errors in the webpack config! 😄 |
Hey there, is there anything stopping this from being released? I'd love to stop hacking around the issue in my webpack config. |
I am sorry, I know I said I will release it, My apologies |
Getting an error when trying to use numbro 1.6.2 with webpack.
|
+1 me too. I had to go back to using numeral for now :( |
@BenjaminVanRyseghem any idea when you'll be able to release this? |
done 😄 In numbro 1.7.0 |
Sorry about that @BenjaminVanRyseghem, github didn't let me know I got a reply. I'm seeing the issue too, I'll check this out in a little while. |
This PR fixes #114.
Webpack doesn't seem to like having expressions in a require. The fix required generating an index.js for the language files and loading this rather than looping through using fs.
In short what I've done:
grunt languages
to generate an index file for the languagesrequireDir
as a dependency, now we just load the index file in the testsfs
andpath
but justrequire
the index file directly in theloadCulturesInNode
method