Skip to content

Conversation

@ClashTheBunny
Copy link

This is a quick MVP for different build tools with the lein-template.

It would be useful for creating example applications for each build tool, as requested in https://github.com/shadow-cljs/examples/issues/8

@ClashTheBunny
Copy link
Author

Things to consider fixing up are a better read-me for each like the quickstart-browser and formatting in the style that you like, not parinfer forced style.

@ClashTheBunny
Copy link
Author

Also, the ontology on the location of the shadow-cljs.edn file could be different. It could be just in the general now that I've templated it and it is used for every single option.

@thheller
Copy link
Collaborator

Thanks. Don't know how I feel about this yet though. Kinda not sure if I want to support deps.edn or project.clj as template options.

I will be writing a npm template option as well as JS users won't have lein installed and thus can't use lein templates.

@ClashTheBunny
Copy link
Author

Maybe then just generate a couple examples and check it into the examples directory?

It took quite a bit of searching to find a working project with both a deps.edn and a shadow-cljs.edn.

I mostly wanted to try it out to get the updating of dependencies with something like lein ancient or depot. I couldn't grok the documentation before I saw an example. Now that I do it's pretty obvious how it should work and it works great!

Would it be better to try and get the documentation a little more robust? I don't know how to do that except for a whole example or maybe just the keys of the data-structures needed in each file?

Also, an npm template sounds super cool!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants