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
For contributions it is basically sufficient to create a new directory for your framework that supports `npm install` and `npm run build-prod` and can be then opened in the browser. All other steps are optional. Let's simulate that by copying vanillajs.
452
454
@@ -468,7 +470,7 @@ In most cases you'll need `npm install` and `npm run build-prod` and then check
468
470
469
471
(Of course in reality you'd rather throw out the javascript source files and use your framework there instead of only changing the html file.)
470
472
471
-
## 4.2 Adding your new implementation to the results table.
473
+
## 4.3 Adding your new implementation to the results table.
472
474
473
475
(Notice: Updating common.ts is no longer necessary, super-vanillajs is visible in the result table)
474
476
@@ -506,7 +508,7 @@ The other important, but optional properties for js-framework-benchmark are show
506
508
507
509
You can set an optional different URL if needed or specify that your DOM uses a shadow root.
508
510
509
-
## 4.3 Submitting your implementation
511
+
## 4.4 Submitting your implementation
510
512
511
513
Contributions are very welcome. Please use the following rules:
0 commit comments