balanced-match: Building Jekyll doesn't like the Readme.md
When attempting to build a Jekyll site on Github, I’m getting this error:
I’m getting this error Your site is having problems building: The variable {{a} on line 50 in node_modules/balanced-match/README.md was not properly closed with }}. For more information, see https://help.github.com/articles/page-build-failed-tag-not-properly-terminated/.
About this issue
- Original URL
- State: closed
- Created 7 years ago
- Reactions: 15
- Comments: 15 (2 by maintainers)
Commits related to this issue
- Exclude node_modules in .gitignore https://github.com/juliangruber/balanced-match/issues/22 — committed to StilgarISCA/ClassicArcadeProjects by deleted user 7 years ago
- Update gitignore to try to address issue with gh-pages build Hitting this issue https://github.com/juliangruber/balanced-match/issues/22 but not sure why. — committed to EarthlingInteractive/aframe-geo-projection-component by sbrudz 6 years ago
- Removing rogue README file. https://github.com/juliangruber/balanced-match/issues/22 — committed to mauriceharry/brochure by gregharvey 7 months ago
I fixed it adding node_modules/* as-well (I referenced it above). Just for further notice, if node_modules has already been uploaded to the repository, adding node_modules/* to .gitignore wont be enough. You will need to untrack node_modules from the repository using the following command:
git rm --cached node_modules -r😃Hello dude , Your site is having problems building: The variable {{a} on line 50 in node_modules/balanced-match/README.md was not properly closed with }}. For more information, see https://help.github.com/articles/page-build-failed-tag-not-properly-terminated/
This is showing to me also how I can fix it . I have completed the project but this is final stage where I am stucked . I have to submit it to my college
Reply as soon as possible
@claytron5000 I ‘solved’ the problem by deleting the node_modules directory in the Codecademy subdirectory completely which go rid of the problem and I wasn’t using that at the moment. however, before, it was in the master branch. I have had this package for a while, but only now have I decided to make the publishing source of my GitHub Pages the master branch and this issue came up with it.
Thanks, @TommyJackson85 I finally got it to work.