Richard Dominick

I encountered the same issue when I tried to install globally using `-g`; hence why in the above examples that I gave, I built js-slang from source instead (and subsequently...

> Hi! Also getting this issue in Ubuntu 23.10. Is there any workaround? Im comming from [npm](https://www.npmjs.com/package/sicp) and get this when doing `yarn add sicp`. Hi, was trying to reproduce...

Bug also present for the following sample code (as reported by Grace): ```js const xs = list(2, 3); display_list(list(pair(1, xs), pair(4, xs))); ```

Should we just remove our custom js-slang syntax highlighting and use default JS one? I don't really see it as a "core" feature to maintain our own syntax highlighting rules...

@sayomaki we need to figure out how to resolve the require on ESM error&hellip... it's blocking our gl migration for both frontend and js-slang :( Should we just use Yarn...

@sayomaki I think best to just use latest Yarn. Doesn't hurt anyway.

Perhaps beyond just a runtime check, we also want to support type-checking for typed variants (see #1398).

obsolete: What happens if we want to display the actual value `undefined`?

> Just a heads up that #1645 will likely affect this PR No worries, it's already quite conflicted anyway, though thanks for the heads up!

Is this a duplicate of #1476?