Skip to content
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

The Namespace parser does not allow local paths #5

Closed
strmer15 opened this issue Jan 3, 2024 · 1 comment
Closed

The Namespace parser does not allow local paths #5

strmer15 opened this issue Jan 3, 2024 · 1 comment

Comments

@strmer15
Copy link

strmer15 commented Jan 3, 2024

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.

@mshima
Copy link
Member

mshima commented Jan 3, 2024

@yeoman/namespace only deals with valid namespaces.
Paths should be converted to namespaces at yeoman-environment.
Closing in favor of yeoman/environment#497 (comment).

@mshima mshima closed this as not planned Won't fix, can't repro, duplicate, stale Jan 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants