Dillon Kearns

That sounds like a platform-specific spawn issue. I know that `spawn` can cause problems, [which is why the `cross-spawn` NPM package was created](https://www.npmjs.com/package/cross-spawn#why). I think that would probably fix the...

Thanks for checking. Could you try this: ```shell npm install --save-dev elm-optimize-level-2 npx elm-pages-beta ``` I think the current beta build script is expecting `elm-optimize-level-2` to be on the PATH.

> BTW, is there a develop mode for the beta build? Not yet, but there definitely will be before it goes out of beta! I'm glad that it's working now...

Hello @lukewilliamboswell! Thank you so much for trying it out and sharing this issue. This definitely looks like a Windows-related compatibility issue. There must be some point in the code...

Hello @Narice, I've been thinking about this as well. I think it would definitely be useful to have different starters (skeleton app and blog, for example). I'm still trying to...

Hi @fpapado, thank you so much for pointing that out! As we discussed on Twitter, if you get around to it I would very much welcome a PR here!

The group ones are unfortunate because there's no elm-tailwind-modules equivalent for that. Not sure what the best thing to do for those is, could be adding a no-op or something...

It's an interesting idea, but I imagine most people won't have Tailwind in their setup at all if they're using elm-tailwind-modules so I think this would be confusing. The fact...

For visibility, https://github.com/mdgriffith/elm-optimize-level-2/pull/90 is also related.

Sounds good! Could you also add an example that shows up in the end-to-end code? This would be a good place to add it: https://github.com/dillonkearns/elm-graphql/blob/master/ete_tests/edge-cases.gql That way we'll have the...