The type definitions for web/* do not match the implementation.

[stc1988]

In a recent update, the existing type definitions were moved to web/*, but some modules (such as headers) do not have the web/ prefix. What are the intended module names?

[phoddie]

I'm not entirely sure that I understand the report. My guess is that you are referring solely to the module specifiers of the TypeScript declarations in $MODDABLE/typings/web. Some of those use the format "web/*" for module specifiers while others omit the "web/" prefix.

I added the typings/web directory to have a consistent place to keep the type declarations for modules that implement Web Standards. But, the use of the "web/" prefix is new and inconsistent. My long term preference is to use the "web/" form because it is more clear of the intent and less likely to have name collisions ("headers" is dangerously general whereas "web/headers" is reasonably clear). For the moment, we should probably follow the existing pattern and revert uses of "web/" to "". We can keep the $MODDABLE/typings/web/ directory.

How does that sound?

[stc1988]

My guess is that you are referring solely to the module specifiers of the TypeScript declarations in $MODDABLE/typings/web. Some of those use the format "web/*" for module specifiers while others omit the "web/" prefix.

Your understanding is correct.

we should probably follow the existing pattern and revert uses of "web/" to "". We can keep the $MODDABLE/typings/web/ directory

Although it is difficult to judge what would be optimal, I think for now it is fine to prioritize compatibility.

[phoddie]

Although it is difficult to judge what would be optimal, I think for now it is fine to prioritize compatibility.

That's fair. When it is time to break things, we should break everything at once. ;)

There is one detail to address. There are three (!!!) WebSocket clients:

1. The original WebSocket client. It uses module specifier "websocket".
2. The ECMA-419 WebSocket client. It uses module specifier "embedded:network/ws/client"
3. The Web Platform's WebSocket client (which is implemented using the ECMA-419 WebSocket client). It cannot use module specifier "websocket". Since it is the newest, I propose we use "web/websocket" as its module specifier. There is no compatibility issue and it adopts the specifier style that others should eventually migrate to.

If that sounds good, we can do a quick fix patch release to get this out and fix the Stack-chan build. Please let me know. Thanks!

[stc1988]

The Web Platform's WebSocket client (which is implemented using the ECMA-419 WebSocket client). It cannot use module specifier "websocket". Since it is the newest, I propose we use "web/websocket" as its module specifier. There is no compatibility issue and it adopts the specifier style that others should eventually migrate to.

That is certainly something we should address right away. I think your proposal should be fine.

[stc1988]

If that sounds good, we can do a quick fix patch release to get this out and fix the Stack-chan build. Please let me know. Thanks!

The build for stack-chan has been fixed on the latest public branch where several issues have been resolved. It would be helpful if a fix patch release could be made.

[phoddie]

Thanks for confirming. We'll try to get a release out today.

[phoddie]

Moddable SDK 7.2.1 is up.