John O'Reilly
02/13/2024, 8:32 PMamakeev
02/15/2024, 1:29 PMJohn O'Reilly
02/15/2024, 2:00 PMamakeev
02/16/2024, 4:24 PMAlexander Tsarev
02/22/2024, 1:56 PM0.3.0-dev-438
version, it should not fail just because of wasm
platform presence (currently only browser one is used). But if it will fail for some other reason - then I'm here :)John O'Reilly
02/22/2024, 2:35 PMAlexander Tsarev
02/22/2024, 2:52 PMid("org.jetbrains.amper.settings.plugin").version("0.3.0-dev-438")
John O'Reilly
02/22/2024, 2:53 PMJohn O'Reilly
02/22/2024, 2:54 PMAlexander Tsarev
02/22/2024, 2:54 PMJohn O'Reilly
02/22/2024, 2:54 PMAlexander Tsarev
02/22/2024, 2:55 PMzsmb
02/22/2024, 2:56 PMmaven("<https://packages.jetbrains.team/maven/p/amper/amper>")
As opposed to the public releases from
maven("<https://maven.pkg.jetbrains.space/public/p/amper/amper>")
Alexander Tsarev
02/22/2024, 2:57 PMJohn O'Reilly
02/22/2024, 3:02 PMJohn O'Reilly
02/22/2024, 3:09 PMdependencies:
that don't have support for wasm......can I "factor these out" like with gradle where you can say group wasm and non-wasm dependencies?Alexander Tsarev
02/22/2024, 3:10 PMJohn O'Reilly
02/22/2024, 3:14 PMJohn O'Reilly
02/22/2024, 3:25 PMwasm-app
?John O'Reilly
02/22/2024, 3:29 PMJohn O'Reilly
02/22/2024, 3:30 PMsrc@noWasm
etc and other targets seem to be working fineJohn O'Reilly
02/29/2024, 6:27 PM0.3.1-dev-420
(was getting errors with one I had been using)....doesn't look like that includes wasm
platform as one above did?