You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
it's quite obvious that developers using the package.json will add the necessary attributes like name and homepage themselves, but for first time users it might be confusing that this grunt template's grunt tasks fails due to missing package attributes (used in the banner config). The outputted warning with a fresh install is:
Running "concat:dist" (concat) task
Warning: An error occurred while processing a template (Cannot read property 'name' of undefined). Use --force to continue.
Should the generated package.json include placeholders or empty values for all attributes used in the banner, and maybe when using the package.json generator print a notice to edit those.
I can provide a PR for this, if needed.
The text was updated successfully, but these errors were encountered:
Yes, I was bit by this and spent several hours on it. So Kontur, thanks for entering the the issue, and no, for first time users, it's not at all obvious that a project that "Create[s] a basic Gruntfile with grunt-init" fails to create a basic gruntfile that works out of the box. The point of "Hello World", it seems to me, is that it works when you DON'T yet know the environment well, without debugging it.
The way I got rid of the error was to comment out the banner altogether.
Hey,
it's quite obvious that developers using the package.json will add the necessary attributes like name and homepage themselves, but for first time users it might be confusing that this grunt template's grunt tasks fails due to missing package attributes (used in the banner config). The outputted warning with a fresh install is:
Should the generated package.json include placeholders or empty values for all attributes used in the banner, and maybe when using the package.json generator print a notice to edit those.
I can provide a PR for this, if needed.
The text was updated successfully, but these errors were encountered: