Issue

When building any produced output package from this templater, the templates fail to build due to nodecg being undefined (see command for generating schemas).

Suggested solution

nodecg-cli should be added as a dependency / peer dependency / noted as a required global dependency when using these templates.

☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.

Version 2.4.0 of generator-node was just published.

This version is covered by your current version range and after updating it in your project the build failed.

generator-node is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

Version 4.17.9 of lodash was just published.

This version is covered by your current version range and after updating it in your project the build failed.

lodash is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

I was unable to use yo nodecg , due to a syntax error present at line 61 of: generators/app/index.js :

}, this).then(function ({name}) {

The bold curly brackets were given as the cause.

Edit: Sorry, it seems the install worked when i upgraded my node from version 4 to the latest.

Description

In the final output bundle, @types are showing up in the direct dependency section of the package.json file. These should be under devDependencies instead.

Are you willing to help fix?

ye

(Originally was incorrectly posted to generator-nodecg/#56)

nodecg-cli has been a bit unloved in the past year or two. It's not been kept up-to-date with changes happening in NodeCG itself. Specifically, it doesn't know about all the current package manifest properties, and it still recommends ~0.8.0 as the default compatibleRange.

This project should be given a once-over to ensure it is sync'd with NodeCG itself.

Version 0.5.1 of deep-extend was just published.

This version is covered by your current version range and after updating it in your project the build failed.

deep-extend is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

The generator prompts you to answer some questions that I think are a bit unclear to answer to someone just setting up a new bundle. For example, "Is this a "single instance" graphic?" -- without any context, this is hard to understand what is meant by it. Does this mean the graphic is only in one scene in OBS? The graphic is only used in one way with a single replicant populating its data (ie: same graphic, different replicant of data is used in parallel)?

In addition, the question regarding React is a bit unclear - some folk (myself included) might want React for their Dashboard but not for Graphics. I think it might be a bit better to be a bit clearer on the prompt for what it's doing / where.

I think another spot that could be helpful for clarification would be "panel name" versus "panel title". I put "Dashboard" in for the first option, had that get changed to dashboard, and then saw the prompt for the second question have the suggestion / autofill of "Dashboard" and got a bit confused as to what was meant by the first question. IE: Is it auto filled off the prior answer or off of a standard for Dashboard panels?

NodeCG v2 is Coming Soon ™️ and will natively support TypeScript. As such, we should offer an option to have generator-nodecg output a TypeScript-ready bundle template.

☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.

Version 5.3.0 of generator-license was just published.

This version is covered by your current version range and after updating it in your project the build failed.

generator-license is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

Reproduction steps:

1. Have Node and npm installed, using nvm.
2. Run yo nodecg in an entirely empty folder.
3. Answer prompts normally.
4. See below error message (should maybe be a warning?)

Environment:

• Node version: v18.16.1
• NPM Version: 9.8.0
• Windows 11, run in pwsh preview through Windows Terminal.

Expected behavior

Either:

• detect I am using npm somehow magically
• prompt me and ask what package manager I'm using

Do not fall back to npm without confirming with end-user that that's the desired behavior, IMO, to avoid running into annoying potential symlink issues further down the line.

Description

Due to the lack of a .travis.yml file setup to run with pull requests or releases, Travis CI doesn't have any builds on record for this repository. Thus, the link & image in the README are broken.

The URL should, regardless, point to: https://travis-ci.com/github/nodecg/generator-nodecg, rather than that path without the /github/ in the URL.

Suggested Fix Options

• Setup Travis CI
• Delete the broken link + broken image from the README.

The generator outputs a string, but the current format is an object.

As already mentioned in PR: #79, supporting program arguments could give some benefits:

• re-allow some sort of Windows test?
• allow integration into other tools (for example: I may develop an IntelliJ plugin for nodecg development, if I can find time for it => interacting with the generator over stdin/out would not be fun...)

Version 1.7.1 of yeoman-test was just published.

This version is covered by your current version range and after updating it in your project the build failed.

yeoman-test is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

The generated package is actually broken / does not build, because glob as of version 10 does not do default export anymore.
(See: isaacs/node-glob@26673b9)

Version 2.4.0 of chalk was just published.

This version is covered by your current version range and after updating it in your project the build failed.

chalk is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

Hi,
First things first: thanks for this great project, really helps to getting started and also speeds up development further down the line.

Just found that there are a lot of old / vulnerable dependencies, so a wanted to-do something about it. (updating everything to what was currently available as stable)

In the process i discovered multiple thing. For example that yeoman-test@7 is not compatible with CommonJS anymore (See: yeoman/yeoman-test#164). So furthermore I ported everything to ES-Modules in the process.

Summary of what I did:

• update dependencie
• port everything to work with ES-Modules
• switched to native mocha (instead of ts-mocha), because had problems with that: (related: piotrwitek/ts-mocha#70)
• changed to commonly used *.spec.ts format for test, instead of plain *.ts
• by updating packages being able to get rid of some @types packages, by using native typescript versions

=> See pull request: #79

Further ideas:

• ES-Modules: (still could get some optimisations using new features, but just wanted to get it working for this Issue/PR - I may do improvements here myself following later)
• enable dependabot for this repo, to get automatic updates in the future. any specific reason it is disabled?

I have been unable to install the generator using the documented command.

$ npm install generator-nodecg
npm ERR! code ENOVERSIONS
npm ERR! No valid versions available for generator-nodecg

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/inaki/.npm/_logs/2021-02-14T14_54_25_234Z-debug.log

It seems that it is not published to npm.

I have been able to install it running
npm install https://github.com/nodecg/generator-nodecg

☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.

Version 3.2.0 of npm-name was just published.

This version is covered by your current version range and after updating it in your project the build failed.

npm-name is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

It is currently 128 + 144(n-1) pixels. Don't know if it's the best way to describe it but can note it somehow.

This project got some get some refactoring.
Here a list of things I found during my recent development of ES-Module port (see: #78 and #79):

Just a list to have them collected and address whenever fits, not necessary to "fix" straight away.

• enable dependabot for this repo, to get automatic updates in the future. any specific reason it is disabled?
• refactor according to more ES-Module like practices. For example (and some example resources for this
  • .join is discoreged because URL and some function support it natively (https://stackoverflow.com/questions/46745014/alternative-for-dirname-in-node-js-when-using-es6-modules, https://blog.logrocket.com/alternatives-dirname-node-js-es-modules/, )
  • fully get rid of require and replace require.resolve, once import.meta.resolve becomes stable (https://stackoverflow.com/questions/54977743/do-require-resolve-for-es-modules)
  • convert leftover commonjs (.prettierrc.cjs)
  • ...
• yeoman: replace deprecated .withPrompts with .withAnswers
• re-introduce some sort of windows test (maybe in conjunction with: #80 ?)
• exclude package-lock from linting (npm run fix): npm i produces different styled file...
• add full .idea folder to gitignore: i have more stuff in there - any reason not excluding the full folder?
• Probably should add node 18 to ci-test, because nodecg recommends v18?
• ...

I intend this issue to stay open for quite some time at least and be updated with any new ideas / suggestions, so feel free to comment.