Closed Apollon77 closed 2 years ago
Hm ... should we kick nodejs 10? at least for testing?
Oh, yeah, after some quick research I think upgrading the node version for the linter workflow could fix the CI pipeline :)
aahh yes the linting was still done in nodejs 10. changed
wtf ... https://github.com/mcollina/node-coap/runs/4122430279?check_suite_focus=true#step:5:4
works locally ... strange
Hmm, maybe the error is caused by the caching step?
Caching step? Could be ... lets see
Hmm, my other theory would be that it is a node 16 problem. The installation fails under both Ubuntu and Windows using that node version, the others seem to be fine.
what we should do?
PS: (because just noticed it) ... do we need to publish the "test" dir in npm too? (in fact we did)
PS: (because just noticed it) ... do we need to publish the "test" dir in npm too? (in fact we did)
Oh, sorry, that is a very good point! I will change that for the typescript version. Or can we publish a 0.26.1 from a different branch?
what we should do?
From what I've seen doing another quick search this problem might actually be related to the caching. Maybe we could try to comment that step out
But yes I will comment out
Okay, my cache theory is disproven :D :/
Ok, reson seems to be the eslint update and other packages ...
Maybe downgrading eslint to 7.x.x (for now) could solve the problem?
just did that :-)
Totals | |
---|---|
Change from base Build 1427561781: | 0.0% |
Covered Lines: | 1131 |
Relevant Lines: | 1244 |
This was it
happy review ;-)
Hm ... should we kick nodejs 10? at least for testing?