No preview when using custom renderer with --root-dir=...

[atrofimov-sc]

What's wrong?

When I use a custom renderer, I see nothing except a message saying it connected. It talks to a window that's in another tab via post-message, but doesn't have an iframe to talk to it!!

Steps to reproduce

Followed custom renderer tutorial. The only thing I changed was adding --root-dir=src/dev because by typescript rules, all *.ts files have to be under root, and the root is src, and I don't want the fixture to be bundled, so it's in src/dev folder. But that breaks the UI!

Screenshots

Useful info

• Cosmos version. - latest

• Cosmos config.

 "$schema": "http://json.schemastore.org/cosmos-config",
  "port": 5000,
  "rendererUrl": "http://localhost:5050",

• Server terminal output.

[Cosmos] Using default cosmos config
[Cosmos] See you at http://localhost:5000
[Cosmos] Generated src/cosmos.imports.ts
[Cosmos] Generated src/cosmos.imports.ts
[Cosmos] Generated src/cosmos.imports.ts
[Cosmos] Generated src/cosmos.imports.ts
[Cosmos] Generated src/cosmos.imports.ts
[Cosmos] Generated src/cosmos.imports.ts
[Cosmos] Generated src/cosmos.imports.ts

• Browser console output.

Empty

Additional context

N/A

I think it's supposed to open a iframe, but there aren't any iframe at all in the cosmos UI.

[ovidiuch]

Hi @atrofimov-sc, sorry for all the confusion, I guess the custom bundler guide could be improved but there are so many variations in user setup and this is not a trivial task. The easiest thing to get past this step is if you provided a public repo that reproduces your setup (and the issues you are facing). I'll be able to clone it and tell you exactly what's missing. Let me know if you can provide this, thanks!

[atrofimov-sc]

I'll try to do a repro, but time is hard to come by right now.

I'll say I'm still able to use the product by specifying "rootDir": "src", in the config. Though the cosmos.imports.ts is still in the wrong folder (would like it to be under src/dev). The erroneous behavior only if the --rootDir setting is set via a flag.

[ovidiuch]

@atrofimov-sc Did you try setting exposeImports to "dev/cosmos.imports.ts" in your Cosmos config?

https://reactcosmos.org/docs/configuration/cosmos-config#config-options

[atrofimov-sc]

Yes I have. I'm sorry for still not having done a repro, but the full command was cosmos --expose-imports --rootDir=src. When I specify these in the cosmos.config.json instead of the CLI, it works. That's what I'm doing now.

[ovidiuch]

If for whatever reason you prefer passing those options via CLI args you can also pass a path to --expose-imports like you do to --rootDir.