Felix Kling

I can't repro this btw. The `displayName` shows up in the result. What does your `./my-component.js` look like?

Oh, the `displayName` handler only looks for explicit `displayName` properties. You want it to also return the inferred name from the class or function name, right?

I don't know, will have to look into this. Seems reasonable to me though. PRs are also welcome ;)

This works: ``` return j(file.source).find(j.Comment).forEach(path => path.prune()).toSource(); ``` https://astexplorer.net/#/gist/1ac239fc11f0c274540e680420313c34/d4a78b1e7ff1eff4f1828e939e545bbf78fde1aa I was hoping that ` j(file.source).find(j.Comment).remove().toSource();` but it looks like `remove` is only defined for `Node`s and a comment is not...

If this is still an issue for you, could you provide a concrete flow example for which this breaks?

It's not possible right now, since we don't run our own server. But we have to solve the parse situation anyway, so probably afterwards :)

@jamesmcnamara You can go to `/settings`, which should redirect you to `/users//settings` and load the settings editor. Hovering over JSON keys there should show tooltips and there shouldn't be any...

@jamesmcnamara That is strange indeed. Honestly I don't know if it's broken only for dotcom and S2. It seems weird that it would only happen for those two. If you...

@jamesmcnamara yay! Thank you for confirming 😃 I'll try to find out what's up with the foreign module error.

@jamesmcnamara FWIW I don't see that foreign module error when running it locally (non-bazel). Do you see that only with bazel? To avoid letting this get stale, maybe we can...