question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Docs: Better (cli/js) options documentation.

See original GitHub issue

The issue

nodemon-webpack-plugin is a simple webpack plugin that launches nodemon.

The plugin simply pass-through a user-provided configuration object to the nodemon function.

Users repeatedly (#2, #8, #89, #117, #123) find it hard to figure out how to provide options to this function due to lack and disperse documentation.

I have added an example on nodemon-webpack-plugin’s README, but questions keep on coming.

It seems highly reasonable that such documentation should exist in this repo and not the plugin’s one. Because it is the nodemon function API that needs documenting - this has nothing to do with the plugin.

Related pages on this repo:

What I normally do is look at the latter, then search the code to confirm the option is programmatically supported.

Possible solutions

It would probably be beneficial to create a central markdown page with all the various options, with their cli and json/js variants. Something along the lines of https://www.typescriptlang.org/docs/handbook/compiler-options.html.

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Comments:5 (2 by maintainers)

github_iconTop GitHub Comments

1reaction
remycommented, Aug 17, 2020

Feel free to pr against the wiki then: https://github.com/remy/nodemon/wiki - not sure what’s missing from the cli, IIRC it’s all there on --help options, but happy to take a pr on that too if it’s sensible.

1reaction
Izhakicommented, Aug 17, 2020

Because the API is that of nodemon, not the plugin. The plugin uses the API of nodemon, as-is (it takes an object and simply passes it on to nodemon). If the nodemon API is documented on another repo, you have two sources of truth. The API lives in one repo (nodemon), the documentation in another (the plugin).

To be honest, you can ignore the plugin story altogether, and instead consider the issue raised here to be:

Can we have documentation for the options available when using nodemon as a requirable?

Read more comments on GitHub >

github_iconTop Results From Across the Web

SoftwareBrothers/better-docs: Beautiful toolbox for jsdoc ...
Documentation toolbox for your javascript / typescript projects based on JSDoc3 with @category, @component and @optional plugins. This is how it looks: Example....
Read more >
Document Service | Apps Script - Google Developers
This service allows scripts to create, access, and modify Google Docs files. // Open a document by ID. var doc ...
Read more >
Understand the basics of privacy in Google Docs, Sheets ...
When you use Google Docs, Sheets, & Slides, we process some data to offer you better experiences in the product. Your information stays...
Read more >
Google Docs | Google Cloud Skills Boost
We will discuss your sharing options and examine collaborator roles and permissions. You will learn how to manage versions of your documents.
Read more >
The 32 Best Google Docs Add-ons - Zapier
They're better than their add-on alternatives we tried. Google Keep. to build documents quickly from notes and web clips. Google Keep in Google ......
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found