Generators provide an API for managing files within your workspace. You can use generators to do things such as create, update, move, and delete files. Files with static or dynamic content can also be created.
The generator below shows you how to generate a library, and then scaffold out additional files with the newly created library.
First, you define a folder to store your static or dynamic templates used to generated files. This is commonly done in a files
folder.
happynrwl/├── apps/├── libs/│ └── my-plugin│ └── src│ └── generators│ └── my-generator/│ ├── files│ │ └── NOTES.md│ ├── index.ts│ └── schema.json├── nx.json├── package.json└── tsconfig.base.json
The files can use EJS syntax to substitute variables and logic. See the EJS Docs to see more information about how to write these template files.
Example NOTES.md:
Hello, my name is <%= name %>!
Next, update the index.ts
file for the generator, and generate the new files.
import { Tree, formatFiles, installPackagesTask, generateFiles, joinPathFragments, readProjectConfiguration,} from '@nx/devkit';import { libraryGenerator } from '@nx/js';
export default async function (tree: Tree, schema: any) { await libraryGenerator(tree, { name: schema.name, directory: `libs/${schema.name}`, }); const libraryRoot = readProjectConfiguration(tree, schema.name).root; generateFiles( tree, // the virtual file system joinPathFragments(__dirname, './files'), // path to the file templates libraryRoot, // destination path of the files schema // config object to replace variable in file templates ); await formatFiles(tree); return () => { installPackagesTask(tree); };}
The exported function first creates the library, then creates the additional files in the new library's folder.
Next, run the generator:
nx generate my-generator mylib
The following information will be displayed.
CREATE libs/mylib/README.mdCREATE libs/mylib/.babelrcCREATE libs/mylib/src/index.tsCREATE libs/mylib/src/lib/mylib.spec.tsCREATE libs/mylib/src/lib/mylib.tsCREATE libs/mylib/tsconfig.jsonCREATE libs/mylib/tsconfig.lib.jsonUPDATE tsconfig.base.jsonUPDATE nx.jsonCREATE libs/mylib/.eslintrc.jsonCREATE libs/mylib/jest.config.tsCREATE libs/mylib/tsconfig.spec.jsonUPDATE jest.config.tsCREATE libs/mylib/NOTES.md
libs/mylib/NOTES.md
will contain the content with substituted variables:
Hello, my name is mylib!
Dynamic File Names
Section titled “Dynamic File Names”If you want the generated file or folder name to contain variable values, use __variable__
. So NOTES-for-__name__.md
would be resolved to NOTES_for_mylib.md
in the above example.
Overwrite mode
Section titled “Overwrite mode”By default, generators overwrite files when they already exist.
You can customize this behaviour with an optional argument to generateFiles
that can take one of three values:
OverwriteStrategy.Overwrite
(default): all generated files are created and overwrite existing target files if any.OverwriteStrategy.KeepExisting
: generated files are created only when target file does not exist. Existing target files are kept as is.OverwriteStrategy.ThrowIfExisting
: if a target file already exists, an exception is thrown. Suitable when a pristine target environment is expected.
EJS Syntax Quickstart
Section titled “EJS Syntax Quickstart”The EJS syntax can do much more than replace variable names with values. Here are some common techniques.
- Pass a function into the template:
// template fileThis is my <%= uppercase(name) %>
// typescript filefunction uppercase(val: string) { return val.toUpperCase();}
// later
generateFiles(tree, join(__dirname, './files'), libraryRoot, { uppercase, name: schema.name,});
- Use javascript for control flow in the template:
<% if(shortVersion) { %>This is the short version.<% } else { for(let x=0; x<numRepetitions; x++) { %> This text will be repeated <%= numRepetitions %> times.<% } // end for loop} // end else block %>
// typescript filegenerateFiles(tree, join(__dirname, './files'), libraryRoot, { shortVersion: false, numRepetitions: 3,});