doingweb / grunt-metalsmith Goto Github PK

npm WARN deprecated [email protected]: This package was split into two simpler plugins: metalsmith-layouts and metalsmith-in-place

metalsmith: {
      options: {
        "plugins": {
          "metalsmith-markdown": {},
          "metalsmith-permalinks": {
            "pattern": ":title"
          },
          "metalsmith-templates": {
            "engine": "jade",
            "directory": "./templates"
          }
        }
      },
      src: "./contents",
      dest: "./dist"
    },

when ./dist doesnt exist (which is usual for built folder to be gitignored), grunt metalsmith output:

Running "metalsmith:dest" (metalsmith) task
Warning: Arguments to path.resolve must be strings Use --force to continue.

Metalsmith supports loading plugins as a local npm modules. see metalsmith cli.
Namely:

{
  "plugins": {
    "./lib/metalsmith/plugin.js": true
  }
}

But when i use such form in grunt-metalsmith i get

Warning: Cannot find module './lib/metalsmith/plugin.js' Use --force to continue.

Hello,

With the latest metalsmith, I get his error.

Fatal error: Object #<Metalsmith> has no method 'path'

this was reported here segment-boneyard/metalsmith-templates#29

this has been hence fixed in metalsmith-templates and metalsmith (1.0.1), but since grunt-metalsmith uses an old version

"dependencies": {
    "metalsmith": "^0.11.0"
  }

I get that error.

I am not a node/grunt expert, but deleting the node_modules of grunt-metalsmith solved the issues (so it takes global latest version). not sure how better to solve this.

can't grunt-metalsmith takes the version specified in my package.json ? or can it remove metalsmith from dependency as it always installed?