I get the following error when I try and run your site.
`Eleventy fatal error: (more in DEBUG output)

Error in your Eleventy config file '/Users/thor3/Documents/pack11ty/.eleventy.js'.

EleventyConfigError was thrown

Must use import to load ES Module: /Users/thor3/Documents/pack11ty/node_modules/@sindresorhus/slugify/index.js
require() of ES modules is not supported.
require() of /Users/thor3/Documents/pack11ty/node_modules/@sindresorhus/slugify/index.js from /Users/thor3/Documents/pack11ty/src/_11ty/_utils/slugify.js is an ES module file as it is a .js file whose nearest parent package.json contains "type": "module" which defines all .js files in that package scope as ES modules.
Instead rename index.js to end in .cjs, change the requiring code to use import(), or remove "type": "module" from /Users/thor3/Documents/pack11ty/node_modules/@sindresorhus/slugify/package.json.`

Changing the version of @sindresorhus/slugify/ to 1.1.0 in package.json fixes the issue.

I was not sure how to make a pull request since I have never made one before.

I am having trouble displaying the screenshot on this page, https://pack11ty.dev/news/2020/04/14/layout-and-design/

I noticed the URL had an error. It showed https://res.cloudinary.com/paulportfolio/image/fetch/q_auto,f_auto,w_1600,c_limit/https://gifted-hermann-0987c3.netlify.app//news/2020/04/14/layout-and-design/pack11ty-screenshot.png
, note the 2 forward slashes after app not just 1 like it should be, so I removed the trailing slash in the package.json URL, and the URL now seems correct, https://res.cloudinary.com/paulportfolio/image/fetch/q_auto,f_auto,w_1600,c_limit/https://gifted-hermann-0987c3.netlify.app/news/2020/04/14/layout-and-design/pack11ty-screenshot.png
but the image does not show. I also removed your NHO from the Cloudinary URL in images-responsiver-config.js and put my own in.

What am I doing wrong? The image shows up fine when I run it locally.

• how to create an account
• what is the cloud name
• security settings (see #11)

I deployed to Netlify and the above error stopped the project from building.

At least for documentation and news

hello and thanks for making pack11ty, can't wait to use it.

• i'm having an issue installing pack11ty
• both "deploy to netlfiy" and local builds fail
• both netlfiy and local seem to be having issues with missing folders

locally "npm install" rendors the following error message

• npm ERR! Error while executing:
• npm ERR! /usr/bin/git ls-remote -h -t ssh://[email protected]/11ty/eleventy.git
• npm ERR! xcrun: error: invalid active developer path (/Library/Developer/CommandLineTools), missing xcrun at: /Library/Developer/CommandLineTools/usr/bin/xcrun
• npm ERR! exited with error code: 1

screenshot of some early warning signs too

In development mode:

• Don't inline critical CSS
• Don't run Eleventy if only CSS is modified
• Update browser with new CSS with BrowserSync
• Don't inline critical JS
• Don't run Eleventy if only JS is modified
• Update browser with new JS with BrowserSync

I get an error when I try and build your site.
The error is:

Your configuration is invalid:
{
  "globDirectory": "_site",
  "globPatterns": [
    "./css/additional.*.css",
    "./js/additional-*.*.js",
    "./",
    "./offline-fallback.html",
    "./manifest.webmanifest",
    "./images/logo-192px.png"
  ],
  "dontCacheBustURLsMatching": {},
  "swSrc": "_site/service-worker.js",
  "swDest": "_site/service-worker.js",
  "mode" [1]: "production"
}

[1] "mode" is not allowed
    at runBuildCommand (/Users/thor2/Documents/ideal-waffle-pack11tyjan01/node_modules/workbox-cli/build/app.js:52:19)

So, I removed the "mode" [1]: "production" line from workbox.config.js and things work fine now.

Does that do any harm?

Thanks
Paul

Use https://github.com/addyosmani/critical to generate the critical inline CSS, instead of requiring the developer to separate critical and non critical manually?

See https://github.com/nhoizey/nicolas-hoizey.photo/blob/9af9245386dfed722625b96c75eeea8e952942fd/src/_11ty/_utils/filter-collection.js#L15

I get an error when I try to run your template. I am not a developer but I managed to find a Debug command in the package.json.

Here is the error section:
Eleventy:EleventyErrorHandler Problem writing Eleventy templates: +0ms
Eleventy:EleventyErrorHandler data.page.inputPath.match is not a function
Eleventy:EleventyErrorHandler
Eleventy:EleventyErrorHandler TypeError was thrown: +1ms
Eleventy:EleventyErrorHandler (error stack): TypeError: data.page.inputPath.match is not a function
Eleventy:EleventyErrorHandler at type (/Users/thor2/Documents/test2-pack11ty/src/src.11tydata.js:6:37)
Eleventy:EleventyErrorHandler at layout (/Users/thor2/Documents/test2-pack11ty/src/src.11tydata.js:21:23)
Eleventy:EleventyErrorHandler at ComputedDataProxy.findVarsUsed (/Users/thor2/Documents/test2-pack11ty/node_modules/@11ty/eleventy/src/ComputedDataProxy.js:53:11)
Eleventy:EleventyErrorHandler at ComputedData.getVarOrder (/Users/thor2/Documents/test2-pack11ty/node_modules/@11ty/eleventy/src/ComputedData.js:55:34)
Eleventy:EleventyErrorHandler at processTicksAndRejections (internal/process/task_queues.js:97:5)
Eleventy:EleventyErrorHandler at async ComputedData.setupData (/Users/thor2/Documents/test2-pack11ty/node_modules/@11ty/eleventy/src/ComputedData.js:73:17)
Eleventy:EleventyErrorHandler at async Template.augmentFinalData (/Users/thor2/Documents/test2-pack11ty/node_modules/@11ty/eleventy/src/Template.js:422:5)
Eleventy:EleventyErrorHandler at async Template.getTemplates (/Users/thor2/Documents/test2-pack11ty/node_modules/@11ty/eleventy/src/Template.js:438:7)
Eleventy:EleventyErrorHandler at async TemplateMap.initDependencyMap (/Users/thor2/Documents/test2-pack11ty/node_modules/@11ty/eleventy/src/TemplateMap.js:246:22)
Eleventy:EleventyErrorHandler at async TemplateMap.cache (/Users/thor2/Documents/test2-pack11ty/node_modules/@11ty/eleventy/src/TemplateMap.js:279:5) +0ms

Does this mean anything to you?

Thanks for your help.
Paul

See https://nicolas-hoizey.com/links/2021/07/29/structuring-eleventy-projects/

• love this starter
• thanks for making it available
• i noticed when admiring the google lighthouse scores there was a minor matter with the seo score
• as per the google lighthouse details: "Document does not have a meta description. Description text is empty."
• i would submit a pull request fix but i don't quite understand the logic with pack11ty's site/global data? most 11ty themes/starter seem to use a site.json file for global but it looks like pack11ty is taking a different approach? (though it's 1:30am where i am atm, so maybe i'm just too tired to see it?)

See https://manu.ninja/turning-manu.ninja-up-to-11ty/#calculate-related-posts-for-each-post

Template Head - Link Source Webmention

The nunchucks <head> for WebMentions should not be hard coded.

<link rel="webmention" href="https://webmention.io/pack11ty.dev/webmention" />
<link rel="pingback" href="https://webmention.io/pack11ty.dev/xmlrpc" />

I think that should be populated from $(domain)? I don't know if that is a global or not to add to njk head?

• <title> and <meta property="og:title" content="…" />generation
• <meta name="description" content="…" /> and <meta property="og:description" content="…" /> generation
• <meta property="og:image" content="…" /> generation

Allows changes in content organization or permalink computing without breaking links inside the site.

Currently standing on one foot with just a few PostCSS features (scss syntax, imports, nesting, simple variables and hashes), it might be interesting to move to true Sass.

node-sass + postcss?

Use node-sass for Sass compilation, but keep using PostCSS for hashes?

https://github.com/ianrose/deventy/blob/master/package.json#L11

Gulp?

If so, how to deal with hashes, not native in node-sass CLI? Build with gulp and add gulp-rev?

If we add gulp, why not move JS build to gulp too? 🤷‍♂️

Rollup?

Using Rollup to build CSS seems counter intuitive, as it looks like you can't build just CSS, it has to be injected in some JS build.

But having both JS and CSS (Sass) built with the same tool might me better for DX.

It will be easier for people to understand, as it is the common way used elsewhere, and it will better separate this from technical stuff in package.json.

Me and @bcomnes (mostly him) are maintaining an up to date fork of npm-run-all over at: https://www.npmjs.com/package/npm-run-all2

(And yes, I did notice this through your new @stackaid profile, https://www.stackaid.us/github/nhoizey, but I have not claimed that project there so I will not get any money for the switch, just noticed that you were using an abandoned module 🙂 )