You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flagon.apache.org by "Joshua Poore (JIRA)" <ji...@apache.org> on 2019/08/07 14:19:00 UTC

[jira] [Commented] (FLAGON-431) Killing nodemon example server throws lifecycle error on node.js v12.7.0

    [ https://issues.apache.org/jira/browse/FLAGON-431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16902106#comment-16902106 ] 

Joshua Poore commented on FLAGON-431:
-------------------------------------

Probably just need to wait for nodemon to catch up to 12.7.0. 12.7.0 is effectively still in development by npm. They support v10 and v11 through october before they go into maintenance.

> Killing nodemon example server throws lifecycle error on node.js v12.7.0
> ------------------------------------------------------------------------
>
>                 Key: FLAGON-431
>                 URL: https://issues.apache.org/jira/browse/FLAGON-431
>             Project: Flagon
>          Issue Type: Bug
>          Components: UserALE.js
>    Affects Versions: UserALE.js 2.1.0
>         Environment: node.js 12.7.0
>            Reporter: Joshua Poore
>            Assignee: Joshua Poore
>            Priority: Minor
>             Fix For: UserALE.js 2.1.0
>
>
> example server builds and logs as expected. however, killing it (^C) results in nasty npm ELIFECYCLE error referencing nodemon. Likely that nodemon doesn't fully support npm v12.7.0.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)