withastro / astro-repl Goto Github PK

I know I'm not the most active so I may have missed something, but I was poking around and noticed going to https://play.astro.build/ gives me a 404: NOT_FOUND error:

404: NOT_FOUND
Code: DEPLOYMENT_NOT_FOUND
ID: cle1::2tjrt-1630717807343-6390f851331e

play.astro.build might be available. Click here to learn how to assign it to a project.

I'd post a screenshot but my PC is acting up at the moment so copy/paste is the best I can do for now :(

Setting the class attribute to a dynamic value in the REPL causes an error.

<h1 class={"foo"}>Hello, Astro!</h1>

If Firefox I see Reference Error: astro is not defined and in Chrome I see Error: Expected ")" but found "astro"

In a local Astro project, it adds the class name as expected. Attributes other than "class" seem to work with dynamic values in the REPL.

Given that this repo is not being maintained, and given that StackBlitz supports Astro, time to deprecate + archive?

As per https://discord.com/channels/830184174198718474/1030567593637064869/1032686184612245504
nate (he/him) said:

I'm not sure if we see a ton of value in getting astro.build/play back up and running when tools like StackBlitz have support for Astro now. That was built in a time where there weren't any other tools that could run Astro, so we needed our own to debug the AST.

jasikpark said:

maybe we can add a deprecation notice to the built site + archive the repo?

What version of astro are you using?

https://play.astro.build

What package manager are you using?

What operating system are you using?

Chrome Android

Describe the Bug

Link to Minimal Reproducible Example

https://astro.build/play#EQegDghg5gpgziACtGA6CcAuAnA9sALmABkBFAC1IFE4AxOAQQGMAJOAYSYYFcH2GA7tgDicAEIAmMQBViAaQYAvGABEAWsygMqYgGwATaQA0AZgwDyUKgFkxAOwBKATQAMUAEZQA1gE8A6qTCABzs7ADKAJIupGImalQOcl4MAFIAlimKfH5qYBJhlAA2YXBQKgCO5gwqTmIAVioqALZhKU4+DBFymGkMpHZ+EJhBTBFN1gxgDmX6wgxqRhKIuAoqKcliAKoM0hJQrIpB2wxwTDBiAgzCTQ4CxGLWACwArAwMaaQAjLhBtMJqJlYAE5dLI4KQmogxE0NGIAMxMWiffRqFhaABqimkYBSp0YLAAci5Hpc6ilsNgwGpELpNkYWPpHoViNIqCoIilNgAPDxOXEOXApEy4HxQWjoppOCRNJjEGAORAOFxqGBw9FwlJ2bikbL8ALzKhcgROIzSQpeIzYT5OCDYPwE6y4BhclIAN2wXloz1IrvIcwYiAYYiYagcaTSwj8ihYYmuXjgLBcinYTnRhSgQJYuigLlw5CgYQENj8ifMLCCiiouGINTgKi5whUUH0VFIKWImwA1ASnNgBMJuF5SM8h49zDqxFQjFAxDA1OxHhAwExtXwtIVaP2CtYwj4JNIguR2JqCesWIoxFDyBFyOR9MQ-E5yF5yg5sO7sHByGAqASvHIqEUCBaC8dgxGIbh2RSC4mAETZ0UeOwIAcLkID6WwdQYGAIGEGJsEQYgfkUFJHmkCIA0KBgfFwuEwAEOphC8JwnDqKgmCBLwLjSKh2kTaxNicEIJG4lRdAkdhEAkN4GG9TsWBeAB2KgqFItIWGIcxpGSBhaDUXRyGkbAqFobAwl2TZ2G4LpuEKchzDgTZiH0TtEC5KyuTSNQghYSDcAkdEIHYAk6i8ZTs2wKBpG7RQ7HYKBHhUMIuCFUh0QU5gBB8XQUnKUhiHYYgwBMCIYE8bFmLEcwHGeARMAJZ4YAiOwivMTZhAiJwVDsHwgQU8gAFoBBSIJpFIgRsU2JoGG5J1XljIM-H0Y1Cn60h9DEFgBDEBxhCoKBzDAUgoGeJguRUQoXD8FRPTY0Y4WrMQnGEJgTHIJhEDqEwgQYOQBGut4nDgCI6jQpwBDhQqBAiMIwgYCACXOMQwBYNJakeeouCaOpXVITAnSMKg0giT5dAcchvrhiR3GcOBGP+9qdKoIMnFoCIoHIWH1HtAw6kQwQtOEJw-DEfQWFSTZnnIiJSDgbBOGsBk4E7AQWDCAk5GEFh7TCFwgXcbFaHYcxrB8HwmE7FJEFxcoxBs8pkLALwVEMOQTY0R4oFdYCGBcYhrDkFRECgEwHAYCRyD8WhHk2XB6sjrQtHYBzSFIbE5FoS7KvTKhfD8EryCaFgmGxARXULh1yGwJ9QrkR5yl3Ix3BcIaVAXIEqDkSXhEwKAIC5CQPIqMJrCBNCXAkc5PkECJni5PxMEQaQXBcMJdBsPhNlZiwJbEMJ0TgZ52B5OwxCjHxNj8T5FEeKsjB8TJHmIdEFkKXamEYiB77hdwIBkWndGsOYIO0hFASEUEwOoPhXSbFOrEBw7IGDAAADSgCYLgJoYBcB2BgHYTACB2DoMwdg3B6AsB4EICQCg1A6CMFYBwLgvB+BwlKKUUgcJe4CHYBAP6vB9ClGIApCI0IghwF8DJWgUBrC6DkC4FQLhnR2CMOwUgcgnCFEAmIKAwhvRwioOUCQpB4xeEQKUdgQQOitjEOQFg2AsznVwDYQ2WhEDBR8LQWGiBKJiE8kGLs2AIidi5NYWgGQmDyOAEAA

• component filename increment problem
  Step to reproduce:

1. Add new component => shown component.astro
2. Add new component => shown component1.astro
3. delete component.astro
4. create new component => shown component.astro
5. create new component (❌ user couldn't add new component)

screenshot:

• removing default import when add new component
  just thought that if we add default import syntax to Page.astro, it could be a problem in the future when user delete component.astro, import syntax is still there. my suggestion was keep user importing manually since the mental model from developer to just import when it's needed (this behavior is common in svelte repl)

What package manager are you using?

yarn

What operating system are you using?

Ubuntu

Describe the Bug

The Astro REPL is not working on Firefox (v93). The spinner is spinning forever without any output (not only preview but HTML and JS also). And the REPL is slower on Firefox compared to Chrome.

Steps to Reproduce

The REPL should output the results

Link to Minimal Reproducible Example (Optional)

https://astro.build/play