Got stuck in creation process of new components

[NonPolynomial]

Tell us about the issue you are experiencing

Got stuck in creation process of new components with new groups in new astrum projects.

What behaviour would you expect?

I can create a new component in a new initialized astrum project.

How can this issue be replicated?

$ astrum init ./pttrns/
$ astrum new foo/bar

Screenshots / Screencast

Your environment

Platform:
OS Version: Windows 10
Node Version: 10.13.0
NPM Version: 6.1.0
Yarn Version: 1.9.4
Astrum Version: 1.9.5

[nod74]

Hi, I had the same problem, took me very long to figure out that astrum does not work with newer Versions of node.js. I could get it running with version node-v8.3.0.

[NonPolynomial]

yeah, I know that it did work on my machine some time ago.
but now my tech stack is predefined and I have to use that Node version.
would like to use astrum as pattern library tool :/

What drives me crazy is, that there is no Exception message or something, WHY it doesn't work with the newer Node version...
Maybe some uncaught Promise rejections?

[joelpierre]

Use NVM you can downgrade your Node version when using Astrum

[NonPolynomial]

Use NVM you can downgrade your Node version when using Astrum

For me personally thats not a problem, but that doesn't solve the problem with a predefined tech stack.
In some of my projects, I'm not able to change the node version.

[nod74]

we had problems get astrum to work online, and the "typekit" made the problems so deleted the typekit option in the json file. Might be the solution or the fix for this Bug

[mdalberto]

Is there any plan/eta on work to get this to run on the latest Node.js version (I'm on Windows and running a down grade version is off the table)?

[joeangry]

I've submitted a pull request that fixes this hopefully it'll be merged in!