-
-
Notifications
You must be signed in to change notification settings - Fork 17
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
Pass namespace for helper.registerDependencies #17
Comments
FWIW If you're using |
I am not using |
@lijunle can you paste your code. It'll help when trying to figure out what is the issue/bug you're running into. |
@lijunle It's been a while since the last ping on this issue. Should we assume you aren't able to share your code / close this or do you think you'll have a chance to get that together? |
Sorry, Currently, I am using such a hack to resolve it: helpers.registerDependencies = function (env, dependencies) {
dependencies.forEach(function (dependency) {
env.register.apply(env, dependency);
});
}; |
I was facing the exact same problem. Locally, yeoman-enviroment was working correctly and retrieving the correct namespace for the specific path. But while running on jenkins for CI, the generator was not found. What I did is to require the specific generator class and registered under the correct namespace |
This issue is stale because it has been open 15 days with no activity. Remove stale label or comment or this will be closed in 5 days |
In helper.registerDependencies, there are two ways to register generator dependency.
Environment.prototype.namespace
is not smart enough to auto detect my namespace because I am writing generator in scope package. My main generator reports the composing generator is not found.The text was updated successfully, but these errors were encountered: