Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unknown compiler exceptions mess up REPL state #89

Closed
Conduitry opened this issue Apr 25, 2017 · 1 comment
Closed

Unknown compiler exceptions mess up REPL state #89

Conduitry opened this issue Apr 25, 2017 · 1 comment

Comments

@Conduitry
Copy link
Member

This has resurfaced, or never went away. I can't figure out what I do to trigger it, but it's not hard. It may have something to do with putting something that causes a compilation error into a child component, even temporarily.

The REPL app gets into a weird state where changes to one component affect multiple components, and the options in the dropdown menu do not always match the current names of the files.

@Conduitry
Copy link
Member Author

It might be triggered by the compiler throwing an exception that the REPL doesn't know how to deal with (e.g., because of a bug in the compiler, rather than an issue we found in the user's component). If I go to https://svelte.technology/repl?version=1.18.0&example=nested-components and type in something that makes the compiler crash (e.g. {{yield}} next to another element, bug), the REPL gets into a bad state and seems to stay that way until I refresh the page.

@Conduitry Conduitry changed the title REPL: Weird bindings with multiple components Unknown compiler exceptions mess up REPL state Apr 25, 2017
Rich-Harris added a commit that referenced this issue Apr 26, 2017
repl: in CodeMirror component, deal with `error.loc` being undefined
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant