⚡️ Support 11ty !!! npm init @vitejs/app ➜ eleventy

[oneezy]

Clear and concise description of the problem

Vite + 11ty

I want the benefits of using 11ty's powerful yet simple static site generator that supports multiple templating engines alongside Vite's powerful yet simple dev server/ build system. Together they will provide an amazing developer experience and workflow.

Suggested solution

This is what I want:

npm init @vitejs/app my-eleventy-app --template eleventy

Could this ever be a possibility @yyx990803 @zachleat ?

Alternative

Vite + 11ty Projects

There's been a few projects created that attempts merging the two together

eleventy-with-vite

I'm currently using this one with success (by @fpapado)
https://github.com/fpapado/eleventy-with-vite

vite-plugin-eleventy

The project is still in alpha stage but shows a lot of promise (by @Snugug)
https://github.com/Snugug/vite-plugin-eleventy
https://snugug.com/musings/eleventy-plus-vite/

Additional context

I originally started the discussion here #1861 (comment) but @Shinigami92 had suggested I make a feature request.

Validations

• Follow our Code of Conduct
• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

[oneezy]

I just want to quickly point out that this is issue #4211

42 is the answer to the ultimate question of life, the universe, and everything
11 is Eleventy

It's a sign guys... Lol

[Shinigami92]

Just to repeat my point of view:
Every additional framework we add natively to vite repo we need to officially also support it, and I think this template is not in scope for vite.

Therefore a place like https://github.com/vitejs/awesome-vite is maybe a better place for such templates and plugins.

BUT as I said, this is just my opinion and we will bring it up in one of our next team meetings 🙂

[patak-dev]

Great spirit and marketing for the proposal 🙌🏼

I also think that we should keep this in awesome-vite. If we include 11ty, why not including VuePress, VitePress, and the list will just keep growing. The scope of create-vite is to quickly scaffold a simple Vite app with popular frameworks to test Vite (and maybe use it as a base for simple apps or prototypes). A general scaffold app is not in the scope of vite core, as it will be too much maintenance burden for this repo and the team. Each framework should have its own app scaffold scheme, like SvelteKit for svelte. It would be great too see a page about Vite in each framework with detailed instructions to how to get started, @oneezy maybe once the options for 11ty are mature enough you can send a PR to the 11ty docs or work with them to create scaffold options that play nicely with their own ecosystem. We need that each framework/lib takes this responsibility so we are able to scale these solutions and the maintenance of docs involved.

[oneezy]

Haha.. thanks! 😅

That makes a lot of sense @patak-js . After reading the comments it does sound more suitable for awesome-vite. I believe @Snugug has been on top of that and aligning his plugin to work with 11ty's v1 release. I guess I was just doing a little pre-marketing for everyone to build awareness lol..

Vite is such an awesome tool and I don't think a lot of devs know about it yet so I'm just doing my part.

[patak-dev]

That is a great attitude @oneezy, I hope that we end up with formal docs in 11ty at one point 💯
And looking forward to seeing these options in awesome-vite. Let's close this issue then for the time being, if create-vite changes its scope we can revisit this call.