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
Copy file name to clipboardExpand all lines: README.md
+34-16Lines changed: 34 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
-
# Microsoft Edge - 2025 web platform top developer needs
1
+
# Microsoft Edge - 2026 web platform top developer needs
2
2
3
-
This repository contains the data and scripts that are used to generate the [Microsoft Edge - 2025 web platform top developer needs](https://microsoftedge.github.io/TopDeveloperNeeds/) dashboard.
3
+
This repository contains the data and scripts that are used to generate the [Microsoft Edge - 2026 web platform top developer needs](https://microsoftedge.github.io/TopDeveloperNeeds/) dashboard.
4
4
5
5
For more information about the dashboard, see these articles on the Microsoft Edge blog:
6
6
@@ -24,9 +24,11 @@ Features are based on the features part of the [web-features project](https://gi
24
24
25
25
*`webFeaturesID`: the ID of the feature in the [web-features](https://github.com/web-platform-dx/web-features/) repo.
26
26
*`rationale`: a list of reasons why this feature is important for our dashboard. Each reason is an object with the following string properties `{ description, link }`.
27
-
*`wpt`: a string starting with `/results`, and including the optional request parameters that's used to retrieve WPT test results on the wpt.fyi site.
27
+
* One test source field:
28
+
*`wpt`: a string starting with `/results`, and including optional request parameters, used to retrieve WPT test results from wpt.fyi.
29
+
* or `test262`: for features tracked in Test262 instead of WPT. Set this to the feature name as returned by the https://data.test262.fyi/features.json API (for example: `Temporal`).
28
30
29
-
**If you change the `wpt` URL after you've already generated the WPT results, set `wptOverride:true` on the feature object, then run `npm run generate` and `npm run update-wpt` again to update the WPT results for this feature. Later, remove the `wptOverride` field.**
31
+
**If you change the `wpt` URL after you've already generated the WPT results, set `forceUpdateResults:true` on the feature object, then run `npm run generate` and `npm run fetch-results` again to update the WPT results for this feature. Later, remove the `forceUpdateResults` field.**
30
32
31
33
For example:
32
34
@@ -43,10 +45,25 @@ For example:
43
45
}
44
46
```
45
47
48
+
For a feature tracked in Test262 instead of WPT, use `test262` (and omit `wpt`):
49
+
50
+
```json
51
+
{
52
+
"webFeaturesID": "temporal",
53
+
"test262": "Temporal",
54
+
"rationale": [
55
+
{
56
+
"description": "Temporal is highly requested by developers",
If the feature corresponds to a group of features from the web-features repo, make the following changes:
47
64
48
65
*`name`: define a name for the group of features.
49
-
*`webFeaturesIDs`: change this field's type to an array of the IDs of the features in the web-features repo.
66
+
*`webFeaturesID`: change this field's type to an array of the IDs of the features in the web-features repo.
50
67
51
68
For example, the Scrollbar styling group below is a group of three different web-features:
52
69
@@ -70,37 +87,38 @@ In addition, you can provide the following optional fields:
70
87
*`name`: to override the name coming from the web-features repo.
71
88
*`description`: to override the description coming from the web-features repo.
72
89
*`spec`: to override the spec (or specs) coming from the web-features repo.
90
+
*`graphNote`: a string that will be shown as a note below the graph for this feature on the dashboard. This can be used to provide additional context about the data shown in the graph.
73
91
74
92
## Generating the dashboard data
75
93
76
94
1. Update the dependencies:
77
95
78
96
*`npm run bump`
79
-
97
+
80
98
This updates to the most recent version of web-features, BCD, and playwright, as well as other dependencies.
81
99
82
100
1. To update the computed feature data file:
83
101
84
102
*`npm run generate`
85
-
103
+
86
104
This re-generates `site/_data/features.json` based on `features.json`.
87
105
88
-
1. To retrieve the latest WPT revision for this week:
106
+
1. To retrieve the latest WPT revisions and test262 run dates for the dates we care about:
89
107
90
-
*`npm run get-wpt-shas`
91
-
92
-
This adds more entries into the `historical-shas.json` file, which is needed to retrieve WPT test results.
108
+
*`npm run update-dates`
93
109
94
-
1. To retrieve the WPT test results:
110
+
This updates the `wpt-shas.json` and `test262-dates.json` files, which are then needed to retrieve WPT and test262 test results.
95
111
96
-
*`npm run update-wpt`
97
-
98
-
This fetches the missing WPT results for our features based on the `historical-shas.json` file, and puts them in `site/_data/wpt.json` as well as generates front-end files in `site/assets/`.
112
+
1. To retrieve the test results:
113
+
114
+
*`npm run fetch-results`
115
+
116
+
This fetches the missing WPT and Test262 results for our features based on what's in `wpt-shas.json` and `test262-dates.json`, and puts them in `site/_data/testResults.json` as well as generates front-end files in `site/assets/`.
99
117
100
118
1. To build the site
101
119
102
120
*`npm run build-site`
103
-
121
+
104
122
This generates the dashboard website in the `docs` directory.
0 commit comments