jsinterface

found the time to test this too, starting from the point where you taught me how to opt out of libadwaita, i compiled with `cargo build --release --no-default-features --features wayland`...

Oh, and mind you, i had to checkout the v0.3.3 tag, because on the latest main, and several commits back, `cargo build --release` on crostini has started failing with ```...

I am experiencing this too. On one phone with android 9 the chrome (pwa) shortcuts are there, but on another with android 11 they are missing from KISS. It's default...

This is a very ambiguous syntax between JSX and TS. You can see in the stack trace that it's being treated as JSX. We could expect independent parsers to accomdate...

a full stack trace: ``` Failed to patriate typescript "file:///mnt/chromeos/GoogleDrive/MyDrive/blik/rauch_2010_socketio/0/lib/socket.ts" due to SyntaxError: Unexpected token (98:9) at pp$4.raise (file:///mnt/chromeos/GoogleDrive/MyDrive/blik/haverbeke_2012_acorn.js:2473:13) at TypeScriptParser.raiseCommonCheck (file:///mnt/chromeos/GoogleDrive/MyDrive/blik/tyrealhu_2023_acorn_typescript.js:5208:44) at TypeScriptParser.raise (file:///mnt/chromeos/GoogleDrive/MyDrive/blik/tyrealhu_2023_acorn_typescript.js:5214:29) at pp$9.unexpected (file:///mnt/chromeos/GoogleDrive/MyDrive/blik/haverbeke_2012_acorn.js:509:8) at pp$9.expect...

in short: ```js export async function parse(source, syntax = "javascript", options = {}) {// interpret language syntax. let {Parser}=await import("./haverbeke_2012_acorn.js"); let typescript=syntax==="typescript"; if(typescript) Parser=await import("./tyrealhu_2023_acorn_typescript.js").then(({default:plugin})=> Parser.extend(plugin({dts:options.source?.endsWith(".d.ts")}))); let comments=[]; let scope=Parser.parse(source,{ecmaVersion:2022,sourceType:"module",onComment:comments,locations:typescript});...

oh ok sorry, your question wasn't clear grammatically. I had the exact line in the parsed file that is throwing the error linked in the opening comment: > parsed file:...

found the reason for this, it's actually the const type assertion syntax above, which is in irredeemable conflict with jsx, as acknowledged before here: https://github.com/TyrealHu/acorn-typescript/issues/47 my solution for that is...

Yes, well I'm not using npm, but building dependencies from source so that I can have the ability to maintain/customize them instead of patching arbitrary build outputs. Not necessarily React...

that's alright, thank you! 2 of them: - no redundancy of "shared" modules if I want to bundle eg. "react" and "react-dom" (etc) separately, by "shared" being a truly modular...