Skip to content

docs(internalization): add typescript examples and fix params as promise #49075

docs(internalization): add typescript examples and fix params as promise

docs(internalization): add typescript examples and fix params as promise #49075

Triggered via pull request December 16, 2024 16:12
Status Success
Total duration 3m 2s
Artifacts 4

build_and_test.yml

on: pull_request
Determine changes
11s
Determine changes
build-next  /  build
55s
build-next / build
optimize-ci  /  Graphite CI Optimizer
3s
optimize-ci / Graphite CI Optimizer
build-native  /  build
35s
build-native / build
validate-docs-links
16s
validate-docs-links
Matrix: test unit
Waiting for pending jobs
rust check  /  build
rust check / build
test cargo unit  /  build
test cargo unit / build
ast-grep lint
10s
ast-grep lint
rustdoc check  /  build
rustdoc check / build
test next-swc wasm  /  build
test next-swc wasm / build
test cargo benches  /  Test
test cargo benches / Test
test next-swc wasi  /  build
test next-swc wasi / build
test devlow package  /  build
test devlow package / build
Matrix: test prod
Waiting for pending jobs
Matrix: test dev
Waiting for pending jobs
Matrix: test integration
Waiting for pending jobs
Matrix: Test new tests for flakes (dev)
Waiting for pending jobs
Matrix: Test new tests for flakes (prod)
Waiting for pending jobs
Matrix: test ppr dev
Waiting for pending jobs
Matrix: test ppr prod
Waiting for pending jobs
Matrix: test turbopack dev
Waiting for pending jobs
Matrix: test turbopack development integration
Waiting for pending jobs
Matrix: test turbopack production integration
Waiting for pending jobs
Matrix: test turbopack production
Waiting for pending jobs
test ppr integration  /  build
test ppr integration / build
types and precompiled  /  build
56s
types and precompiled / build
test firefox and safari  /  build
test firefox and safari / build
Matrix: Run devlow benchmarks
Waiting for pending jobs
Matrix: Test new tests when deployed
Waiting for pending jobs
report test results to datadog
0s
report test results to datadog
Fit to window
Zoom out
Zoom in

Annotations

10 warnings and 10 notices
optimize-ci / Graphite CI Optimizer
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
optimize-ci / Graphite CI Optimizer
Invalid authentication. Skipping Graphite checks.
Determine changes
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
validate-docs-links
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
ast-grep lint
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
thank you, next
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
to-resolved-in-loop: turbopack/crates/turbopack-browser/src/ecmascript/evaluate/chunk.rs#L221
Calling `chunk.ident().to_string().to_resolved().await?` in a loop could be a doing a lot of work sequentially. Consider producing an iterator of futures and using `try_join`.
to-resolved-in-loop: turbopack/crates/turbopack-core/src/introspect/utils.rs#L77
Calling `key.to_resolved().await?` in a loop could be a doing a lot of work sequentially. Consider producing an iterator of futures and using `try_join`.
to-resolved-in-loop: turbopack/crates/turbopack-core/src/introspect/utils.rs#L95
Calling `key.to_resolved().await?` in a loop could be a doing a lot of work sequentially. Consider producing an iterator of futures and using `try_join`.
to-resolved-in-loop: turbopack/crates/turbopack-core/src/introspect/utils.rs#L105
Calling `key.to_resolved().await?` in a loop could be a doing a lot of work sequentially. Consider producing an iterator of futures and using `try_join`.
to-resolved-in-loop: turbopack/crates/turbopack-core/src/introspect/utils.rs#L127
Calling `key.to_resolved().await?` in a loop could be a doing a lot of work sequentially. Consider producing an iterator of futures and using `try_join`.
to-resolved-in-loop: turbopack/crates/turbopack-core/src/reference/mod.rs#L184
Calling `RawModule::new(*source).to_resolved().await?` in a loop could be a doing a lot of work sequentially. Consider producing an iterator of futures and using `try_join`.
to-resolved-in-loop: turbopack/crates/turbopack-ecmascript/benches/analyzer.rs#L96
Calling `Environment::new(Value::new(ExecutionEnvironment::NodeJsLambda(
to-resolved-in-loop: turbopack/crates/turbopack-ecmascript/src/manifest/chunk_item.rs#L87
Calling `SingleOutputAssetReference::new(*output_asset, key)
to-resolved-in-loop: turbopack/crates/turbopack-ecmascript/src/manifest/loader_item.rs#L119
Calling `SingleOutputAssetReference::new(
to-resolved-in-loop: turbopack/crates/turbopack-ecmascript/src/typescript/mod.rs#L161
Calling `TsConfigTypesReference::new(

Artifacts

Produced during runtime
Name Size
turbo-run-summary-build-native
102 KB
turbo-run-summary-build-next
137 KB
turbo-run-summary-lint
239 KB
turbo-run-summary-types-and-precompiled
239 KB