What should the filename be of a file with no default exports?

[Istanful]

The rules state that a file with a default export should exactly match the name of the default export. What should the filename be of a file with no default export? Should such a file exist at all?

Consider the following file:

export function getItem(key) {
  return localStorage.getItem(key);
}

export function setItem(key, value) {
  return localStorage.setItem(key, value);
}

In this case the guidelines does not seem to have a clear answer. I would lean towards localStorage.js, but I could see how LocalStorage.js could be considered as well.

[ljharb]

I agree there’s no clear answer here. However I’m not sure what the point is of making this module when local storage itself already exists and could be referenced directly.

[Istanful]

@ljharb Absolutely! localStorage is just a silly example. I've seen several developers use the same pattern for other stuff, and I'd love something to point at when the situation arises! :D

[ljharb]

The mental model here is that a module is its default export, and it has its named exports. In this case, it’s matching the LocalStorage api, so any name that connotes “it has localstorage methods” is probably fine - i don’t think explicit guidance is needed for every case.

[Istanful]

@ljharb I agree. It is a nitpick.

I think for me, the preferred naming would either be PascalCase as it could have been expressed as a class with static methods. OR the guidelines could forbid files without default exports.

Feel free to close the issue if you think either of those are silly rules. :)

[ljharb]

I’m not sure if they’re silly, but i don’t think they’re common enough to warrant an explicit rule, so I’ll close it.

[xiaohubei]

来信已收到，我会尽快回复你，谢谢来信！