-
Notifications
You must be signed in to change notification settings - Fork 78
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
General: Error building locale #3839
Comments
Actually, we're using locale on more than one page, and I do now see that it is necessary. |
I think some would definitely bring locale in with it as needed, wondering if it works without it added explicitly? But probably another we should fix here cc @EdwardCoyle |
@awbuboltz are you using the Locale component API directly in your app? If not, you may not need to build it this way. However if you do use API like It's not clear to me why this isn't building but agreed it definitely should. 👍 |
Yeah, we do use it directly, isRTL(), setting the locale manually, getting the calendar(), things like that. |
Hey @EdwardCoyle, I'm still seeing the same AfZa error when running npm run build -- --components=locale, is it working for you? |
@awbuboltz I just realized this issue was still in the |
@awbuboltz I tested this on master branch i had actually merged this already to master april 29 So which branch were you testing on or where and is it maybe old? To test i pulled master...
I think this should work from my tests either if you use our master branch and test it or if you import 4.28.0-rc.0 on your end it should work in that too? |
Hmm.. I'm still seeing |
Hmm not seeing it..
|
I also tested this on both @awbuboltz can you try the following and let me know what you find? Run these in your terminal: npm run clean
npm run build -- --components=locale --dry-run When that completes:
|
========= IDS Enterprise Builder ========= Searching files in
JS Source Code: 58 files ✓ Completed dry run! Generated files are available in the "temp/" folder. |
// Foundational ====/ // Mid ====/ // Complex ====/ |
That doesn't seem right.. I see the same output when running with ids-enterprise@4.28.0-rc.0 as well. |
Seeign similar output using master. // Foundational ====/ // Mid ====/ // Complex ====/ |
After some testing it seems that we've got build errors happening only on Windows. I'll have to make a PR to adjust some code that might only be dealing with Unix-style paths. |
Thanks guys! Just had our first fully successful build using 4.28.x! |
Describe the bug
Including locale in a custom build is giving an error.
To Reproduce
Steps to reproduce the behavior:
npm run build -- --components=locale
[!] Error: 'AfZa' is not exported by src\components\locale\cultures\af-za.js, imported by temp\components.js
Expected behavior
Should be able to generate a build that includes locale
Version
Platform
Additional context
We've always been building locale as a component on one of our pages.. is that even necessary?
The text was updated successfully, but these errors were encountered: