Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

node.walk is not a function

Open
#265 4 comments 4 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
elm, javascript, node.js

Research direction

Start by reproducing the reported npm run build command and inspect the stack-trace locations in node_modules/tailwindcss/node_modules/postcss-selector-parser/dist/selectors/container.js and tailwindcss/lib/util/formatVariantSelector.js. Done means the build no longer fails with node.walk is not a function when the reported class is used.

Written by the indexing model from the issue text.

Description

Hello, I am using postcss with Parcel and Tailwind in my project and everything has been going smoothly until I tried to use a certain feature of Tailwind: it happens when I add the "group-hover" part to the following lines:

div
    [ class "group-focus:text-red-500 cursor-pointer"
    , onClick ActivateFeatureInput
    ]
    [ text "Add feature" ]

The output on the command line is:

C:\dev\som>npm run build

> build
> parcel build src/index.html --dist-dir dist --public-url /dist/

× Build failed.

@parcel/transformer-postcss: node.walk is not a function

  TypeError: node.walk is not a function
      at C:\dev\som\node_modules\tailwindcss\node_modules\postcss-selector-parser\dist\selectors\container.js:228:23
      at Selector.each
  (C:\dev\som\node_modules\tailwindcss\node_modules\postcss-selector-parser\dist\selectors\container.js:207:16)
      at Selector.walk
  (C:\dev\som\node_modules\tailwindcss\node_modules\postcss-selector-parser\dist\selectors\container.js:224:17)
      at C:\dev\som\node_modules\tailwindcss\node_modules\postcss-selector-parser\dist\selectors\container.js:228:23
      at Selector.each
  (C:\dev\som\node_modules\tailwindcss\node_modules\postcss-selector-parser\dist\selectors\container.js:207:16)
      at Selector.walk
  (C:\dev\som\node_modules\tailwindcss\node_modules\postcss-selector-parser\dist\selectors\container.js:224:17)
      at Selector.walkPseudos
  (C:\dev\som\node_modules\tailwindcss\node_modules\postcss-selector-parser\dist\selectors\container.js:300:17)
      at C:\dev\som\node_modules\tailwindcss\lib\util\formatVariantSelector.js:114:18
      at Root.each
  (C:\dev\som\node_modules\tailwindcss\node_modules\postcss-selector-parser\dist\selectors\container.js:207:16)
      at Object.finalizeSelector (C:\dev\som\node_modules\tailwindcss\lib\util\formatVariantSelector.js:113:9)


C:\dev\som>

Final details: I'm on Windows, Node version is v17.0.1, and I'll paste my dependency versions here for good measure:

{
  "devDependencies": {
    "@parcel/transformer-elm": "^2.6.2",
    "cssnano": "^4.1.10",
    "daisyui": "^2.20.0",
    "elm": "^0.19.1-5",
    "elm-format": "^0.8.5",
    "elm-hot": "^1.1.2",
    "elm-test": "^0.19.1-revision4",
    "node-elm-compiler": "^5.0.4",
    "parcel": "^2.6.2",
    "parcel-bundler": "^1.12.5",
    "postcss": "^8.4.14",
    "sass": "^1.23.3",
    "tailwindcss": "^3.1.6"
  },
}
Dominant language
JavaScript
Stars
214
Forks
63
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from postcss/postcss-selector-parser

All issues in postcss/postcss-selector-parser

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.