Template-literals-cli NPM

template-literals-cli

Templates so literal, a barbarian can do it

Provides a simple way to build ES6 Template Literals into static html files with an optional yaml or json config/data file.

Getting started

Install via npm install template-literals-cli -g
Create a config/data file using either YAML or json. For example mydata.yml:

fire_hot: true
exclamations: 
  - 'UYGH!'
  - 'GRRAH!'
  - 'OOAH!' 
colors:
  - 'red'
  - 'orange'
  - 'yellow'

Create a template file which exports a default function. For example touchfire.js:

export default (config)=>`
<html>
    <body>
        <h1>${ config['fire_hot'] ? config['exclamations'][Math.floor(Math.random() * config['exclamations'].length)] : 'Wha'}</h1>
        
        <h3>${ config['exclamations'].join(' ') }</h3>
        
        <div>
            ${ config['fire_hot'] ? config['exclamations'].map((exclamation, index)=>`
                <span style="color: ${config.colors[index]}; padding: 1rem;">${exclamation}</span>
            `).join(''):'' }
        </div>
    </body>
</html>
`

Build the file into dist/touchfire.html using template-literals --config config.yml --outdir dist touchfire.js
(optional) Start the http server of your choice in dist/ and visit http://localhost/touchfire.html. Optionally you can build again using template-literals --config config.yml --outdir dist --indexes touchfire.js and then visit http://localhost/touchfire/ if you want a prettier url.
(optional) Add the npm script below to your project's package.json so can just run npm run build instead of remembering your exact build command:

{
"scripts": {
    "build": "template-literals --config config.yml --outdir dist --indexes src/*.js"
    }
}

Note that the wildcard is expanded by your terminal and therefore may not work on Windows/wherever glob is not available.

Importing other templates

Using templates from other files is easy, just import the desired template like this:

// File: templates/header.js
export default (config)=>`
<nav class="menu">
  <ul>
    <li><a href="#">Home</a></li>
    <li><a href="#">About</a></li>
    <li><a href="#">Contact</a></li>
  </ul>
</nav>
`
// end file

// File: index.js
import header from 'templates/header';
export default (config)=>`
<html>
    <body>
        ${ header(config) }
        
        <!-- more content here -->
    </body>
</html>
`
// endfile

Complex logic

If your templates start to get complicated you can always fall back to javascript to handle complex bits - so long as the default export returns a string.

import item_card from 'templates/item_card.js';
export default (config)=> {
  let x = 0;
  let cards = config['items'].map((item)=>{
    return item_card(item, x++);
  });
  return `
     <html>
         <body>
             ${ cards.join('') }
             
             <!-- more content here -->
         </body>
     </html>
  `
}

Injecting environment variables

Occasionally, it's helpful to inject variables at build-time. As of 0.2.0, any key=value pairs after -- will be processed as additional config properties and can even override existing values in the config file.

//myPage.js
export default ({env="prod"})=>`
<html>
<head> ... </head>
<body>

...

${/* Use env to switch between minified and unminified javascript files */ '' }
${env === 'prod' ? `
  <script src="dist/main.min.js"></script>
` : `
  <script type="module" src="main.js"></script>
`}

</body>
</html>
`;

template-literals --config "config.yml" --outdir ./ ./src/myPage.js -- env=dev

A big stick

These overrides have a couple super powers. Take the following config:

{
  "projects": [
    {
      "title": "My Project",
      "figures": {
        "sales_6mo": "/images/sales.png",
        "sales_3mo": "/images/sales2.png"
      }
    },
    // ...
  ],
  // ...
}

Now imagine you need to override the project title. By specifying a key with dot-notation you can change properties deep in your config:

template-literals --config "config.yml" --outdir ./ ./src/myPage.js -- projects.0.title="The Best Project"

And to take things a step further, you can completely override projects.0.figures with a new object by passing JSON as a value:

template-literals --config "config.yml" --outdir ./ ./src/myPage.js -- projects.0.title="The Best Project" projects.0.figures='{"sales_1mo":"/images/sales_1mo.png","sales_3mo":"/images/sales_3mo.png"}'

Final result:

{
  "projects": [
    {
      "title": "My Best Project",
      "figures": {
        "sales_1mo":"/images/sales_1mo.png",
        "sales_3mo":"/images/sales_3mo.png",
      }
    },
    // ...
  ],
  // ...
}

esm minimist yamljs

@infinitebrahmanuniverse/nolb-templ @everything-registry/sub-chunk-2888

2 years ago

3 years ago

3 years ago

4 years ago

4 years ago