`npm start` does not work on Windows about lime-elements

[adrianschmidt]

@calleboketoft Something tries to read the stencil.config.dev.ts file and fails (just like you said), but I don't think it's Stencil, because running npm run build works just fine (when run with cross-env), and that doesn't point to a config file explicitly, but Stencil still uses the stencil.config.ts file.

So I'm wondering if it might not be cross-env that tries to read that file for some reason. I don't know why it would though… Edit: nope, not cross-env. Same thing happens when running without cross-env.

I think it's possible to work around already though (as long as we add cross-env of course): If instead of running npm start, you build the docker container and run npm run dev:watch inside the container, then run npm docz:dev on the Windows machine, everything ought to work… I think… :)

[adrianschmidt]

I can't test this effectively on my virtual machine with Windows because it's too slow to work with without risking a desktop-related head injury… also Docker doesn't seem to work very well inside it.

[calleboketoft]

I really wonder what would try to read the stenciljs config and fails. I'll have another look at it!

[calleboketoft]

If we don't use a custom stencil.config.ts, and run the commands without "--config stencil.config.dev.ts" it works. Is it necessary with custom configs?

[adrianschmidt]

If we don't use a custom stencil.config.ts, and run the commands without "--config stencil.config.dev.ts" it works. Is it necessary with custom configs?

Combining the configs isn't a good solution, since while we can have two different build targets (dev and dist) in the same config file, they cannot use different config options, apart from stuff like the output directory. Which means the dist-build will get polluted with dev-assets, and the dev-build can't be built with relaxed compiler-checks.

But we can switch the configs: Make the dev-config the default one, and the dist-config the custom one. That way dev-builds work on Windows, but you'd have to create your dist-builds in Docker when on Windows. This doesn't affect lime-elements since we build in Jenkins, but it would affect web-component plugins, since they are (as far as I know) built buy consultants on their own machines, at the moment.

I'll try this approach.