Updated JavaScript kernel with typescript, top-level async/await, es module import, promise resolution#111
Conversation
I would hide this from the user as its more related to our implementation than to the usage. |
|
I have changed the way ESM imports are handled, have to verify that it no longer outputs any warnings, otherwise I can add a flag to the jupyter kernel that it should run node with --no-warnings flag |
0div
left a comment
There was a problem hiding this comment.
Looks promising!
There's one thing i do not understand in the ijavascript fork: how do the dependencies change affect the behaviour in it? I don't see them being imported in the code changes?
Also it would be nice to make a PR for each original repo? nice contrib and that way if it's accepted and merged we can use them again in our deps?
I take it the code-interpeter js tests passed with this?
|
Hey Jonas, PR to the original repo would be not very productive as the original projects were abandoned, which is why we had to fork them in the first place. Existing tests pass, I removed the negative scenarios that should no longer be failing. New tests will be in a separate PR. I also confirmed there are indeed no warnings when trying to import the modules. Currently waiting for a deploy of the updated template-manager so we can update the code interpreter template. |
changelog
kernel changes:
issues:
Examples
snippet:
before:
after:
(see my note regarding the warning)
snippet:
before:
after:
snippet:
before:
after: