@@ -56,12 +56,12 @@ together your own tool.
56
56
57
57
[ AllInfo] [ AllInfo ] exposes a Dart representation of all of the collected
58
58
information. There are deserialization libraries in this package to decode any
59
- info file produced by the ` dart2js ` ` --dump-info ` option. See
60
- ` lib/binary_serialization.dart ` and ` lib/json_info_codec .dart ` to find the
61
- binary and JSON decoders respectively. For convenience,
62
- ` package:dart2js_info/src/io.dart ` also exposes a helper method that can choose,
63
- depending on the extension of the info file, whether to deserialize it using the
64
- binary or JSON decoder. For example:
59
+ info file produced by the ` dart compile js ` (before Dart 2.18, ` dart2js ` )
60
+ ` --dump-info ` option. See ` lib/binary_serialization .dart ` and
61
+ ` lib/json_info_codec.dart ` to find the binary and JSON decoders respectively.
62
+ For convenience, ` package:dart2js_info/src/io.dart ` also exposes a helper
63
+ method that can choose, depending on the extension of the info file, whether to
64
+ deserialize it using the binary or JSON decoder. For example:
65
65
66
66
``` dart
67
67
import 'dart:convert';
@@ -102,7 +102,7 @@ The following tools are a available today:
102
102
* [ ` deferred_check ` ] [ deferred_check ] : a tool that verifies that code
103
103
was split into deferred parts as expected. This tool takes a specification
104
104
of the expected layout of code into deferred parts, and checks that the
105
- output from ` dart2js ` meets the specification.
105
+ output from ` dart compile js ` meets the specification.
106
106
107
107
* [ ` deferred_size ` ] [ deferred_size ] : a tool that gives a breakdown of
108
108
the sizes of the deferred parts of the program. This can show how much of
@@ -501,7 +501,7 @@ steps are as follows:
501
501
` --experiment-call-instrumentation`
502
502
503
503
` ` ` console
504
- $ dart2js --dump-info --experiment-call-instrumentation main.dart
504
+ $ dart compile js --dump-info --experiment-call-instrumentation main.dart
505
505
` ` `
506
506
507
507
The flag only works dart2js version 2.2.0 or newer.
@@ -536,14 +536,14 @@ Runtime code analysis requires both an info file and a runtime data file.
536
536
The info file is emitted by compiling a dart2js app with `--dump-info` :
537
537
538
538
` ` ` console
539
- $ dart2js --dump-info main.dart
539
+ $ dart compile js --dump-info main.dart
540
540
` ` `
541
541
542
542
Enable the collection of runtime data by compiling a dart2js app with an
543
543
experimental flag :
544
544
545
545
` ` ` console
546
- $ dart2js --experimental-track-allocations main.dart
546
+ $ dart compile js --experimental-track-allocations main.dart
547
547
` ` `
548
548
549
549
After using your app (manually or via integration tests), dump the top-level
0 commit comments