Igor Minar

Update guidance for @angular/* packages

5

### Bug Report or Feature Request (mark with an `x`) ``` - [ ] bug report -> please search issues before submitting - [x] feature request ``` ### Versions. ```...

module worker typings support

2

[Module worker syntax](https://developers.cloudflare.com/workers/learning/migrating-to-module-workers/) is currently not supported by @cloudflare/workers-types. This means that users don't get the benefits of autocompletion or type checking when they use the new syntax. References: -...

update peer dependency to [email protected]

1

``` npm WARN peerDependencies The peer dependency karma@>=0.9 included from karma-browserstack-launcher will no npm WARN peerDependencies longer be automatically installed to fulfill the peerDependency npm WARN peerDependencies in npm 3+....

Support mounting the same application multiple times

2

Solid-start apps currently boostrap through a side-effect of importing entry-client.HASH.js with script tag in the HTML: ``` ``` This script module is a result of bundling the following code: ```...

Add 2024-03-26 entry point to workers-types

7

adding a new entry point since the last one is from July 2023

version all asset urls

5

we should add version number/build number/sha to urls for all assets so that when we deploy a new build to production we don't have issues with stale browser caches.

It might be because of an uncaught exception in the background page. @mhevery shared this stack trace from the background page with me. It might or might not be related:...

:-) the issue is that if a test run succeeds and then new issues are introduced without resetting the server and the browser, the next text run will succeed again,...

currently we have to use this.spyOn(foo, 'bar'); instead of the usual: spyOn(foo, 'bar');

Selecting a failed test from the list should highlight/jump to the failed line

1

Right now it just select the first line of the test, I'd rather see what assertion failed.