sezna / nps

NPM Package Scripts -- All the benefits of npm scripts without the cost of a bloated package.json and limits of json
MIT License
1.43k stars 93 forks source link

mention tasksfile in roadmap #206

Closed devinrhode2 closed 5 years ago

devinrhode2 commented 5 years ago

What:

Why:

How:

Checklist:

codecov[bot] commented 5 years ago

Codecov Report

Merging #206 into master will not change coverage. The diff coverage is n/a.

Impacted file tree graph

@@          Coverage Diff          @@
##           master   #206   +/-   ##
=====================================
  Coverage     100%   100%           
=====================================
  Files          12     12           
  Lines         396    396           
  Branches       96     96           
=====================================
  Hits          396    396

Continue to review full report at Codecov.

Legend - Click here to learn more Δ = absolute <relative> (impact), ø = not affected, ? = missing data Powered by Codecov. Last update 69aaec2...f8c21c2. Read the comment docs.

sezna commented 5 years ago

This seems pointless, the template wasn't filled out, and perhaps is related to hacktoberfest?

Closed.

devinrhode2 commented 5 years ago

Not pointless. 3 times over the life of the project somebody opened up an issue asking about supporting functions instead of just strings for script/tasks in nps itself. It's been clearly outlined that nps won't be supporting functions for script/tasks. However, if someone wants that they should use Tasksfile.js instead. Who knows, maybe some day somebody comes along and submits this exact same PR.

Sorry I didn't fill out the template, I honestly didn't realize that. As it's just a documentation tweak the only relevant information is the change in the markdown.

Not related to hacktoberfest but thanks for making me feel like a hackathonian or should I say hackathoner or hackathonianer hackathanos hackathor "hacker" is too vanilla for me