You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 9, 2020. It is now read-only.
When I created the bundle in my linux env, the resulting js file doesn't include the *.json files (package config files). I opened a Question in StackOverflow related with this issue, where I explain some details, but the problem is quite simple, my package config paths It's something like:
But my base directory It was something like : "/home/tomcat/.jenkins/.../My Proyect (angular2)", so after some debug, I see that the method getPackageConfigPath(packageConfigPaths, normalized) didn't return anything for the project libs (the same config worked ok in my local env), and I think that the problem is the regExp used to see if the packagename matches in the absolute path defined by packageConfigPaths section, the '(...)' in the absolute path is affecting the regExp match method.
I think that the regExp should be applied only over the packageConfigPaths values , but not on the entire absolute path, anyway I'm not sure, maybe there is a better solution.
The text was updated successfully, but these errors were encountered:
When I created the bundle in my linux env, the resulting js file doesn't include the *.json files (package config files). I opened a Question in StackOverflow related with this issue, where I explain some details, but the problem is quite simple, my package config paths It's something like:
But my base directory It was something like : "
/home/tomcat/.jenkins/.../My Proyect (angular2)
", so after some debug, I see that the methodgetPackageConfigPath(packageConfigPaths, normalized)
didn't return anything for the project libs (the same config worked ok in my local env), and I think that the problem is the regExp used to see if the packagename matches in the absolute path defined bypackageConfigPaths
section, the '(...)' in the absolute path is affecting the regExpmatch
method.I think that the regExp should be applied only over the
packageConfigPaths
values , but not on the entire absolute path, anyway I'm not sure, maybe there is a better solution.The text was updated successfully, but these errors were encountered: