Warn when loading empty mod.nu
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 40.5k
- Forks
- 2.3k
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 85
Description
Related problem
#11157 changed the behavior of empty mod.nu reexporting sibling files and child directories. It fits Nu's philosophy of preferring explicit over implicit but broke my scripts and config with no hint why or how to fix it.
Describe the solution you'd like
Empty mod.nu isn't s sensible construct anymore so I think it'd be helpful to explain users should explicitly export use subcommands and export module submodules and either link to the new documentation or #11133 for rationale.
Describe alternatives you've considered
No response
Additional context and details
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the behavior change described in #11157 and the rationale in #11133. Locate the code and tests responsible for loading an empty mod.nu, then determine how the warning should point users toward explicit export use and export module declarations or the relevant documentation. Done means empty mod.nu produces a helpful warning without changing the intended explicit behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust, shell
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100