We wanted to have a visual approach to design projects,. write Templates in a text form and have the possibility to regenerate everything with the help of protected „own-code“ areas. We'd be so happy to get your feedback on this. Please try it out and hit me up on Intercom in the app itself, via email: paul.coch@generato.com, or simply right here. I'd love to hear what you have to say about it, what you like, what you don't like and how we can approve this to a better developer experience.
generator-your-unique-name, I named it using a scoped package name convention (I looked through you GitHub repository and saw that you added scoped package name support in your v2.4.0 release). However, my generator still isn’t showing up on the Yeoman website. Is there anything special/extra that I need to do for Yeoman to pick up my generator?
env.register(require.resolve('../generators/component1'),
oclif:component1);//await super.generate('component1');
env.run('oclif:component1', (err: any, stdout: any, stderr: any) => {
console.log(err);
});
at Object.<anonymous> (C:/Project/SynapseModernization/2020/cli/src/generators/component1.ts:5:42)) 439:23)
at Module.m._compile (C:/Project/SynapseModernization/2020/cli/node_modules/ts-node/src/index.ts:cli/node_modules/ts-node/src/index.ts:442:12)439:23) -environment/lib/store.js:47:27)
at Object.require.extensions.(anonymous function) [as .ts] (C:/Project/SynapseModernization/2020/js:71:39)cli/node_modules/ts-node/src/index.ts:442:12)
at Object.get [as oclif:component1] (C:/Project/SynapseModernization/2020/cli/node_modules/yeoman-environment/lib/store.js:47:27)
at Store.get (C:/Project/SynapseModernization/2020/cli/node_modules/yeoman-environment/lib/store.js:71:39)
at Environment.get (C:/Project/SynapseModernization/2020/cli/node_modules/yeoman-environment/lib/environment.js:540:48)
at Environment.create (C:/Project/SynapseModernization/2020/cli/node_modules/yeoman-environment/lib/environment.js:613:37)
at instantiateAndRun (C:/Project/SynapseModernization/2020/cli/node_modules/yeoman-environment/lib/environment.js:729:30)
at Environment.run (C:/Project/SynapseModernization/2020/cli/node_modules/yeoman-environment/lib/environment.js:758:12)
at CsGenerator.run (C:/Project/SynapseModernization/2020/cli/src/commands/component1.ts:18:9)
at CsGenerator._run (C:/Project/SynapseModernization/2020/cli/node_modules/@oclif/command/lib/command.js:35:31)
Hey folks - question: i'm trying to use the yeoman-test createGenerator helper method. But i get:
TypeError: console.Console is not a constructor
at new TerminalAdapter (/work/spaces/generator-test/node_modules/yeoman-environment/lib/adapter.js:24:39)I tried to base my logic off of the tests here: https://github.com/yeoman/yeoman-test/blob/bb820da630d9d7ee8d9e7898848e896427e25675/test/helpers.js#L41-L70 but while that works when i run locally, my generator tests don't work.. Any thoughts?
yeoman-environment in node_modules, then print the options.console out.The source code is here: https://github.com/yeoman/environment/blob/master/lib/adapter.js#L24
Hello all, I have started to use yeoman to generate a project and had little issues so far aside from testing. Writing tests is something I'm still learning about but the issue I'm having I just can't seem to make sense of a solution or find more relevant information online or on the docs, I wonder if someone could help me since I'm really curious to know what can be done to solve it and would be a great lesson for me.
How to test this generator properly
The generator makes one or more requests to download a few .zip files, extracts them and copies them to a directory. This can take a variable amount of time and when I write a test to assert file presence what ends up happening is that the assertions occur while the files are still being downloaded.
The code of my generator is open source and can be found here: https://github.com/csalmeida/generator-hozokit/blob/generate-hozokit/generators/app/index.js
This is the test I attempted to write (tried a few more things but all of them have similar results).
'use strict';
const path = require('path');
const assert = require('yeoman-assert');
const helpers = require('yeoman-test');
describe('generator-hozokit:app', () => {
beforeAll(() => {
return helpers
.run(path.join(__dirname, '../generators/app'))
.withPrompts({ projectName: 'Hozokit Test', installWordpress: false })
.then(function() {
// Checks that Hozokit was successfully extracted and present.
assert.file(['../hozokit-test/wp-content/themes/hozokit-test', '../hozokit-test/wp-content/themes/hozokit-test/index.php', '../hozokit-test/wp-content/themes/hozokit-test/templates/base.twig']);
// Checks that Wordpres has not been installed.
assert.noFile(['wp-login.php', 'index.php', 'wp-includes']);
// Checks that no zip files remain on the system.
assert.noFile(['*.zip',]);
});
});
});It also seems that the examples in the docs are written in Mocha but the generator ships with Jest?
Any help from someone experienced in this would be deeply appreciated! 🙏
npm install --global yo
npm WARN deprecated har-validator@5.1.5: this library is no longer supported
npm WARN deprecated cross-spawn-async@2.2.5: cross-spawn no longer requires a build toolchain, use it instead
npm WARN deprecated request@2.88.2: request has been deprecated, see request/request#3142
npm WARN deprecated resolve-url@0.2.1: https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated urix@0.1.0: Please see https://github.com/lydell/urix#deprecated
npm WARN deprecated axios@0.18.1: Critical security vulnerability fixed in v0.21.1. For more information, see axios/axios#3410
added 728 packages, and audited 729 packages in 35s
34 packages are looking for funding
run npm fund for details
4 high severity vulnerabilities
@y-chen the way I do this is with a regEx for instance
this.fs.copy(this.templatePath('../templates/fileToModified.html'),
this.destinationPath('/index.html'), {
process: function (content) {
var regExTitle = new RegExp('title', 'g');
var newContent = content
.toString()
.replace(regExTitle, 'content you wish to add to file');
return newContent;
}
}
);Hope this helps if your question has not already been answered
1 reply
yo my-template -o . --force to force update a template. But it is asking me all the questions for initialization again (eg. projectname ...). Also the ones which are stored in a .yo-rc.json . Do I have to adapt the template to be able to work with the force argument?
