Source Maps, Site Paths and GitHub Actions

Deploying a site friendly to View Source

Part 8 of setting up 11ty dev blog.

Project Scope and ToDos

  1. Static Site Generator that can build the blog and let me host it on Github Pages
  2. I want to write posts in Markdown because I'm lazy, it's easy, and it is how I take notes now.
  3. I don't want to spend a ton of time doing design work. I'm doing complicated designs for other projects, so I want to pull a theme I like that I can rely on someone else to keep up.
  4. Once it gets going, I want template changes to be easy.
  5. It should be as easy as Jekyll, so I need to be able to build it using GitHub Actions, where I can just commit a template change or Markdown file and away it goes. If I can't figure this out than fk it, just use Jekyll.
  6. I require it to be used by a significant percent of my professional peers so I can get easy answers when something goes wrong.
  7. I want source maps. This is a dev log site which means whatever I do with it should be easy for other developers to read.
  • Can I use the template inside of dinky that already exists instead of copy/pasting it?
  • Is there a way to have permalinks to posts contain metadata without organizing them into subfolders?

  • How do I cachebreak files on the basis of new build events? Datetime? site.github.build_revision is how Jekyll accomplishes this, but is there a way to push that into the build process for Eleventy?

  • Make link text look less shitty. It looks like it is a whole, lighter, font.

  • Code blocks do not have good syntax highlighting. I want good syntax highlighting.

  • Build a Markdown-it plugin to take my typing shortcuts [prob, b/c, ...?] and expand them on build.

  • See if we can start Markdown's interpretation of H tags to start at 2, since H1 is always pulled from the page title metadata. If it isn't easy, I just have to change my pattern of writing in the MD documents.

  • Should I explore some shortcodes?

Day 8

Source Maps

So, the Sass source-map is still giving me file:// URLs. This is apparently some sort of weird error in the dart-sass implementation? I found a few issues, all of which seem to point at one issue's set of solutions. But none of these worked for me. I'm not really sure why. I think because dart-sass assumes source maps are only used for local development, not also for public-facing examples like I want. But the top of that thread pointed me at a useful build script example.

Filename Fixes

On the basis of that (which still uses dirname for local file paths) I altered it to match my reality of running a local server"

	const outFile = "/assets/css/style.css";
var result = sass.renderSync({
includePaths: ["**/*.{scss,sass}", "!node_modules/**"],
file: "src/_sass/_index.sass",
outputStyle: "compressed",
sourceMap: true,
sourceMapContents: true,
outFile: path.join(process.cwd(), path.basename(outFile)),
console.log("Sass renderSync result", result);
var fullCSS = result.css.toString();
var map = JSON.parse(;
map.sourceRoot = domain; = JSON.stringify(map, null, "\t");
var fullMap =;

I understand everything that my code is doing here, but the use of process.cwd here is very confusing. It works, for sure! I now have:

	"version": 3,
"sourceRoot": "http://localhost:8080",
"sources": [

The code sample says "HACK 1: Force all "sources" to be relative to project root" but it apparently does this so that dart-sass... gets rid of the project root? I find this process very confusing, I'm adding the project root so Sass can remove the project root? This is fking baffling to me and apparently hits some process that is very badly documented in dart-sass. The other hack "node-sass does not support sourceRoot, but we can add it" at least makes sense. Seems like something you should support! It looks like some iteration of Node-based Sass takes the sourceMapRoot configuration property, but not dart-sass. The documentation and debugging process is very confusing for this because dart-sass links to node-sass for most of its documentation, but node-sass clearly has some features that dart-sass does not, and the fact that issues are often in node-sass that are actually about dart-sass is just a mess.

Anyway, this works now... and it gives me a really useful insight into how the source map is built. I can hack better paths for sources! The paths themselves are useful for the project, but having them at the base of the website sort of irks me. Now I can put them all in a nice sass folder, makes it neat.

{% raw %}

	var newSources = => {
return "sass/" + source;
map.sources = newSources;

{% endraw %}

And I can also change my passthroughs in .eleventy.js.

{% raw %}

"dinky/_sass": "sass/dinky/_sass",
"src/_sass": "sass/src/_sass",

{% endraw %}

If this works correctly on publish, it will resolve the last of my base requirements!

Cache Break with GitHub

Ok, I was thinking about how to handle build-time cache-breaking and realized that there's likely a way to handle getting a cache-break variable at the build stage. There's a plugin for Jekyll to do it, it looks like it does so at least partially via the Github API. It gets a pretty good list of data too. There's also the "Github Context" which is available to GitHub actions. I could call the API during build time, which is what it appears that Jekyll is doing (I didn't really look too deeply into the plugin). But if this data is available in the Actions context... couldn't I export it as a environment variable? Why not try adding that to the Github Actions script?

{% raw %}

        - run: export GITHUB_HEAD_SHA=${{ github.run_id }}

{% endraw %}

Now I should be able to call this in my site data, right? So I'll update the file at src/_data/site.js.

module.exports = (info) => {
return {
lang: "en-US",
github: {
build_revision: process.env.GITHUB_HEAD_SHA || 1.0,
site_url: process.env.DOMAIN,

Huh... about to try this but a thought occurs... should I just export the whole github object? Would that work? Wait... is it already there? Let me try that both ways and see what I get.

git commit -am "Set up new Sass build process and new build vars in use"

Well... the Sass sitemaps built properly, but none of the Github Actions env stuff seemed to have gone off. For some reason calling process.env.GITHUB_JOB just got me deploy. Which is the job name, not a job-run ID. But a step in the right direction, just me mistakenly reading the docs.

What if I set the env at the level of job? I think this means I could probably use GITHUB_SHA, but I want to see what works.

{% raw %}

runs-on: ubuntu-latest
MY_GITHUB_RUN_ID: ${{ github.run_id }}

{% endraw %}

Ah, that did it, so now I know how to use both!

Site Maps

The sitemap plugin looks easy to implement. Let's try that!

Looks good! A little basic as sitemaps go, and if this site gets extensive I may have to figure out file splitting, but there's a lot of flexibility and options in the plugin so I'm not too worried.

git commit -am "Set up sitemap"

Just checking off stuff in this post!

Looks like the Deep Data Merge is up and running already. I'll do a quick double check and it does appear to work fine!

Managing Page Data

RSS feed next. Need to add the collection tag to my posts.json in src/posts in order to have it properly in a posts collection.

"layout": "post.njk",
"description": "Aram is talking about code",
"tags": [ "posts" ]

Huh, I'm getting this in the output now: Benchmark (Configuration): "htmlToAbsoluteUrls" Nunjucks Async Filter took 40ms (8.9%, called 8×, 5.0ms each) and the domain name is wrong in the RSS feed. Found some info on building permalinks that may be useful for my more dynamic link urls, but doesn't seem to be for this. Huh, looks like this generates an Atom feed, not an RSS standard one. Going to rename the file accordingly.

Still no go on getting those URLs set up properly. I need to pass the calculated domain in to the page metadata, but using template tags or JS functions doesn't seem to be doing it. The domain data just isn't going through.

Ok, I had thought the functions in the js layout-based front matter would execute themselves, but it looks like I have to write them to execute in the context of the front matter itself. So now the front matter looks like this:

{% raw %}

"permalink": "feed.xml",
"eleventyExcludeFromCollections": true,
"metadata": {
"title": "Feed for Fight With Tools - Aram's Dev Blog",
"subtitle": "Notes on various projects",
"url": (function(){ return process.env.DOMAIN + "/" })(),
"feedUrl": (function(){ return process.env.DOMAIN + "/feed.xml" })(),
"author": {
"name": "Aram Zucker-Scharff",
"email": ""
"internalPageTypes": [ "feed" ]

{% endraw %}

Looks like the solution was to use a immediately-invoked function there. Working well now!


Looks like there is a straightforward way to handle building a good robots.txt file.

I'll hand build an RSS template so I have an RSS2 feed as well.

git commit -am "Set up various feeds and crawling tools"