Question 1

How to use Pollinate with a private GitHub repository?

Accepted Answer

You can use any Git URL, including private repos, by providing the URL in the command. Ensure your Git credentials are configured for authentication, as Pollinate relies on standard Git operations for fetching templates.

Question 2

Pollinate vs Yeoman: which is better for scaffolding?

Accepted Answer

Pollinate is more lightweight and Git-centric with a declarative schema, ideal for teams already using Git for templates. Yeoman offers a larger ecosystem with generators and interactive prompts, better for complex, multi-step setups.

Question 3

How to add custom Nunjucks filters in Pollinate?

Accepted Answer

Define a 'filters' object in template.json pointing to JavaScript files within the template. These files should export filter functions, as shown in the README's Filters section, enabling extended templating logic.

Question 4

Can Pollinate merge JSON files without overwriting static content?

Accepted Answer

Yes, use the 'merge' key in template.json to specify JSON file pairs, like package.json. Pollinate uses lodash.merge to combine them, preserving static data while injecting variables, detailed in the Merge example.

Question 5

How to run post-generation scripts with Pollinate?

Accepted Answer

Add a 'complete' key in template.json with a command string, such as 'git init {{ name }}'. This executes after file generation, automating setup tasks like initialization, per the README's post-generation hooks.

Question 6

Does Pollinate support environment variables in templates?

Accepted Answer

Not directly mentioned in the README. Data must be passed via CLI, JSON, or other sources; you'd need to pre-process environment variables into these formats, limiting dynamic integration compared to some tools.

Pollinate

What is Pollinate?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions