-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
feat: boundaries #9634
base: main
Are you sure you want to change the base?
feat: boundaries #9634
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
7cc741b
to
42e3344
Compare
53f55cf
to
93929ce
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Only blocker is that we're still depending hitting NPM when fetching the util
dependency for another
package in the test fixture.
async fn boundaries(&self) -> Result<Array<Diagnostic>, Error> { | ||
match self.run.check_boundaries().await { | ||
Ok(result) => { | ||
result.emit(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Out of scope for this PR, but this feels weird to me. What's the intended use of this info? Should it be output by default or gated behind a trace/debug level log?
Description
This is a first pass at a boundaries implementation. We add a top level command
turbo boundaries
that checks your files for invalid imports. We currently check for:Testing Instructions
Added tests via
query
for the three scenarios listed above.