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
Now that yo is updated to use yeoman-generator v4, the @yeoman/namespace dependency is causing issues with local generators being run. See yeoman/yo#797 and yeoman/environment#497.
When I debugged locally, this appears to be due to the NAMESPACE_REGEX not supporting local paths which start with a ./ - the regex looks like it expects there to be an alphanumeric character, or dash, or tilde followed by a series of those same characters. Even if the regex were updated, I'm not sure the code to parse the namespace would work still, since it's expecting specific groups from the regex and this style of getting a generator namespace doesn't seem to make sense there.
The text was updated successfully, but these errors were encountered:
@yeoman/namespace only deals with valid namespaces.
Paths should be converted to namespaces at yeoman-environment.
Closing in favor of yeoman/environment#497 (comment).
Now that
yo
is updated to useyeoman-generator
v4, the@yeoman/namespace
dependency is causing issues with local generators being run. See yeoman/yo#797 and yeoman/environment#497.When I debugged locally, this appears to be due to the
NAMESPACE_REGEX
not supporting local paths which start with a./
- the regex looks like it expects there to be an alphanumeric character, or dash, or tilde followed by a series of those same characters. Even if the regex were updated, I'm not sure the code to parse the namespace would work still, since it's expecting specific groups from the regex and this style of getting a generator namespace doesn't seem to make sense there.The text was updated successfully, but these errors were encountered: