Allow importing Nunjucks macros with a namespace without mounting 'node_modules'

I’ve just moved from the beta to v1.0.0 of the Frontend and I am wondering why you moved from the @ namespace in npm?

I was setting my nunjucks path to the @govuk-frontend folder and then my import path would be, for example, frontend/components/error-summary/macro.njk. I liked this as it was clear where the macro was coming from and it kind of namespaced the govuk stuff, which allowed me to use the same naming conventions, like a components folder etc (and worked the same for SASS frontend/settings/_colours.scss to import the govuk one and then settings/_colours.scss for my project one)

To get around this for nunjucks I just made the include path node_modules so I can specify govuk-frontend/components/... this works fine except for my tests have now gone from ~2s to ~13s. I assume this is because of the vast amount of folders in node_modules, so does anyone have any solutions for this?

[NickColley]

Hey Graham,

Sorry for the delay, we’ve spoken about this as a team.

We want to make this easier so you don’t have to do work around in your own code, but we think doing any of these suggestions will result in a breaking change.

So we’re going to assign this to the 3.0.0 release, let us know if this is blocking you as it may be a while before we do a 3.0.0 release.

Nick

[web-bert]

I think these:

@import "settings/all";
@import "helpers/all";
@import "tools/all";
@import "core/typography";
@import 'core/lists';
@import "objects/width-container";
@import "objects/form-group";
@import "overrides/typography";
@import "overrides/spacing";

Would be nicer like this:

@import "govuk-settings/all";
@import "govuk-helpers/all";
@import "govuk-tools/all";
@import "govuk-core/typography";
@import 'govuk-core/lists';
@import "govuk-objects/width-container";
@import "govuk-objects/form-group";
@import "govuk-overrides/typography";
@import "govuk-overrides/spacing";

Thoughts?