Extensionless extends, includes and imports

Is there any way to provide nunjucks with templates files extension name, so we could drop it in extends, includes and imports.

For example, Instead of

{% extends "layout.nj" %}

use

{% extends "layout" %}

I’ve heard that it’s possible to configure extension name when Nunjucks used in conjuration with Express. But what about other use cases, when Nunjucks used on it’s own, or with Grunt?

[rightaway]

+1 since .njk is now the recommended extension, it would help adoption of it if .njk would be automatically appended where there is no extension provided.

[ArmorDarks]

@carljm posted in https://github.com/mozilla/nunjucks/pull/691#issuecomment-215252873:

I still don’t like #475 – I think the recommended extension should remain a matter only for the documentation and the community, not something that has an actual effect on the behavior. Even if it were configurable, I still don’t see the benefit – it makes your includes etc correspond less clearly to the actual template files, why is that a good thing?

It’s very minor thing, I agree. But it’s just somehow wrong to ask developer specify extension every single time while importing or including something when you’re clearly working in unified environment.

I think closest example here is ES2016, babel, systemjs. When you’re importing other modules, you do not specify .js extension, unless you really need to specify extension for some serious reason. For example, when importing non-standard for system file. In other words, not .js one, but Sass or CSS. or image. It’s just a good design, since system arguably assumes that you by default would require specific to current environment files only, and not anything else. In some sense, it DRYing out code, by removing constantly repeating and really not useful extension.

Same principle used in many other modern systems.

Option to drop extension just makes Nunjucks more unified with them.