Skip to content

Navigation Menu

Explore
By company size
By use case
By industry
View all solutions
Topics
- AI
- DevOps
- Security
- Software Development
- View all
Explore
- GitHub Sponsors
  Fund open source developers
- The ReadME Project
  GitHub community articles
Repositories
- Enterprise platform
  AI-powered developer platform
Available add-ons
Pricing

Search code, repositories, users, issues, pull requests...

Search

Clear

Search syntax tips

Provide feedback

We read every piece of feedback, and take your input very seriously.

Include my email address so I can be contacted

Saved searches

Use saved searches to filter your results more quickly

Name

Query

To see all available qualifiers, see our documentation.

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

vercel / next.js Public

Notifications You must be signed in to change notification settings
Fork 27k
Star 128k

Code
Issues 3k
Pull requests 577
Discussions
Actions
Security
Insights

Additional navigation options

Code
Issues
Pull requests
Discussions
Actions
Security
Insights

Turbopack: Single-graph-traversal and migrate next/dynamic #46989

Sign in to view logs

Sign in to view logs

Turbopack: Single-graph-traversal and migrate next/dynamic

Turbopack: Single-graph-traversal and migrate next/dynamic #46989

Summary
Jobs
- Graphite CI Optimizer
- Determine changes
- build
- build
- validate-docs-links
- build
- build
- build
- build
- build
- build
- Test
- build
- build
- ast-grep lint
- build
- build
- build
- build
- build
- build
- build
- build
- build
- build
- build
- build
- build
- build
- build
- build
- build
- build
- build
- build
- build
- build
- build
- build
- build
- build
- build
- test next-swc wasi
- build
- build
- build
- build
- build
- build
- build
- build
- build
- build
- build
- build
- build
- build
- build
- build
- build
- build
- build
- build
- build
- build
- build
- build
- build
- build
- build
- build
- build
- build
- build
- build
- build
- build
- build
- build
- build
- build
- build
- build
- build
- build
- build
- report test results to datadog
- thank you, next
Run details
- Usage
- Workflow file

Usage Workflow file

Annotations

10 warnings

ast-grep lint step: turbopack/crates/turbopack-core/src/diagnostics/mod.rs#L114

Don't use a Vc directly in a struct

ast-grep lint step: turbopack/crates/turbopack-core/src/source_map/mod.rs#L61

Don't use a Vc directly in a struct

ast-grep lint step: turbopack/crates/turbopack-core/src/source_map/mod.rs#L90

Don't use a Vc directly in a struct

ast-grep lint step: turbopack/crates/turbopack-core/src/source_map/mod.rs#L91

Don't use a Vc directly in a struct

ast-grep lint step: turbopack/crates/turbopack-core/src/reference/mod.rs#L37

Don't use a Vc directly in a struct

ast-grep lint step: turbopack/crates/turbopack-core/src/reference/mod.rs#L52

Don't use a Vc directly in a struct

ast-grep lint step: turbopack/crates/turbopack-core/src/reference/mod.rs#L90

Don't use a Vc directly in a struct

ast-grep lint step: turbopack/crates/turbopack-core/src/reference/mod.rs#L129

Don't use a Vc directly in a struct

ast-grep lint step: turbopack/crates/turbopack-core/src/proxied_asset.rs#L18

Don't use a Vc directly in a struct

ast-grep lint step: turbopack/crates/turbopack-core/src/proxied_asset.rs#L19

Don't use a Vc directly in a struct

ast-grep lint

succeeded Nov 28, 2024 in 13s

Loading

Re-running jobs...

You can’t perform that action at this time.