Components named 'Create' fail confusingly

[pngwn]

I was recieving an error (intermediate value).$$ is undefined and it turns out this is because I named my component 'Create'. I'm guessing this clashes with an internal Create class or function or a javascript keyword (I don't remember it being one)?

This should probably give a descriptive error (I don't know if it could be renamed?). This was incredibly confusing and difficult to work out what was going on. Renaming fixed it.

REPL

[pngwn]

Components named Destroy and Update also break, although the component itself mounts without an issue in this case. I guess this is a similar issue with name collisions.

[Conduitry]

Well this is a new and interesting type of naming conflict, present only in dev mode.

The methods in the object returned by a create_fragment function usually have one-letter names for more compact code. In dev mode, each is given a more descriptive name (via e.g. c: function create() { ... }) so that it can still be called the same way but it will look nicer in stack traces. However, this create shadows any higher-up create (which in this case is the component instance). Similar things will happen in each of the fragment methods.

Making this even more confusing, the REPL by default does not actually show you the dev mode code that it's running and which is causing the error.

[Conduitry]

Presumably the most straightforward way to handle this would be to add the names of each of those methods to the component.usedNames set ahead of time when compiling in dev mode, but we'd need to remember to update that if we ever add another fragment method.

[Conduitry]

Opened #2213, which instead pushes the deconflicting responsibility into each block/fragment, where it probably belongs. This does mean that the component instance will win out and get the create name, while the create method will get the name create_1.