-
-
Notifications
You must be signed in to change notification settings - Fork 2
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
blitz start
broken in 0.8.0-canary.4
#484
Comments
@Skn0tt it seems the gitignore check is crawling the file system to and compiling a list of all ignored files. Is that what it's doing? |
Yup. Didn't know about the |
As can be seen from the stack trace, |
After some investigation, it seems like $ yarn why glob-stream
=> Found "glob-stream@6.1.0"
info Reasons this module exists
- "_project_#@blitzjs#server#vinyl-fs" depends on it
- Hoisted from "_project_#@blitzjs#server#vinyl-fs#glob-stream" |
Found the root-cause, it is indeed related to blitz-js/blitz#365: Gitignore entries starting with a |
Ok cool. Is there a way can do this without actually reading all the gitignore files? Because it causes a performance hit on boot up |
Nope, don't think so. blitz-js/blitz#389 excludes |
It'd be possible to further speed it up by doing an informed glob search based on already-found |
Ok, perfect. Thanks! |
What is the problem?
Steps to Reproduce:
yarn global add blitz@0.8.0-canary.4
blitz new myapp
cd myapp
blitz start
Maybe this is related to changes in blitz-js/blitz#365?
Weird workaround
rm -rf node_modules
yarn
blitz start
-> workscc @ryardley @Skn0tt
The text was updated successfully, but these errors were encountered: