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.
Relative paths for nunjucks imports
See original GitHub issueI have my nunjucks configure path set to node_modules/@govuk-frontend that way when I import govuk macros I use a path that describes where they are coming from (and they are not confused with my own macros):
{% from 'frontend/components/radios/macro.njk' import govukRadios %}
This has been working fine (for things like the footer), however this doesn’t work when a macro template imports other macros - such as radios.
The fix for this would be to use relative paths for the imports. I have tested locally and it works for me…
Issue Analytics
- State:
- Created 5 years ago
- Reactions:1
- Comments:8 (6 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
should we also consider having an ‘all.njk’ like we do for JS and SCSS where we import all components?
Hi, @web-bert thanks for raising this.
Once the team is back on Tuesday, we’ll have a look to see if this is something we’d want to do and if so how we can work this into our backlog. We’ll keep you posted.