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

Why does nucleus.scandir exist with it's constraints? #28

Open
Fishrock123 opened this issue Aug 2, 2016 · 1 comment
Open

Why does nucleus.scandir exist with it's constraints? #28

Fishrock123 opened this issue Aug 2, 2016 · 1 comment

Comments

@Fishrock123
Copy link
Member

I'm not clear on why scandir is useful given it is only able to see into the initial package/zip bundle. If you're running that sort of thing, won't be hard-pathed anyways? It's not like you'll be scanning that kind of user data out of it?

cc @creationix

@creationix
Copy link
Member

I have found it useful to iterate on built-in paths. You might be using generic libraries to consume assets in your bundle.

Would it be possible to implement a node-like require system without some sort of scandir?

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