yeoman VS degit

Tools like yeoman, degit, and cargo generate kept me happy for years. They add basic templating capabilities to the standard git clone but they stop there. You’ll be hard pressed to find tools that go beyond setting up a directory structure.

Yeoman

I don't follow. What you're describing sounds like something akin to either Yeoman or UltiSnips and output-only tools like that don't need to care about whether two pieces of code are semantically equivalent.

Getting back to Wasm and the yo-wasm repo. This repo exists to help you easily create Wasm modules which can be published to OCI registries. The yo-wasm project currently supports publishing to either Azure Container Registry or Hippo and uses Yeoman to generate projects based on templates that are defined in this repo. There are templates for Assembly Script, C, Rust, Swift, and TinyGo. We've added a new template for C#, so let's give it a try.

This happened recently when writing a Yeoman generator to quickly scaffold new projects. I wanted to write something like expect(result).toHaveDevDependency("typescript") to assert that the package.json file generated with the project includes a specified package in its devDependencies.

You can find a few good generators for Yeoman https://yeoman.io/

Yeoman

Hi! Good project you have here! What is your main focus fot it? Being some kind of uber-generator like http://yeoman.io/ or becoming a hosting platform? Case the latter, is on-premise PaaS in the roadmap?

There are a lot of generators/scaffolding tools that can generate a base for you, whether that is the actual structure you want or not can vary a lot, but many of them have quite sensible defaults. It's often a architectural decision how you actually want to structure your code, and isn't really a one side fits all thing. One generator i have used and a lot of the templates there have pretty close to production quality setup (obviously you could always argue about personal preferences and what serves the project in question) is https://yeoman.io/ . It's web focused, but paradigms vary so much between different kinds of development it's pretty impossible to create something that could serve all of them.

The easiest way is to use degit.

Here I am using degit to bootstrap our Ember app since the ember-cli doesn't allow you to create a new Ember app in the name of app.

Instead of starting from the idea of adopting a monorepo, you probably want to start from your pain points and work backwards from there. Standardizing on initial setup can be done w/ scaffolding tools (e.g. degit). Standardizing on configuration can be done w/ libraries (we do this for eslint, jest, etc). After-the-fact alignment can be done w/ codemods (e.g. jscodeshift) and PR tracking tools (IIRC sourcegraph has an offering like this).

Tools like yeoman, degit, and cargo generate kept me happy for years. They add basic templating capabilities to the standard git clone but they stop there. You’ll be hard pressed to find tools that go beyond setting up a directory structure.

If you want "just" the repo without the history, use git clone xyz --depth=1 or npx degit xyz

You could use codesandbox for your initial setup or create a local svelte application using the degit tool. Open a new terminal and run the following command:

There are tools like https://github.com/Rich-Harris/degit you may use. For simpler cases, it may be sufficent to store a template on your local drive and copy it quickly with a command like rsync. If you have a couple of utility functions or similar you keep using, consider creating an npm package.

To kick of the project, let first make a simple Svelte app. Degit package is a simple way to start building apps with Svelte. Feel free to replace bar-chart with any project name you want.