fail to use pnpm create @ast-grep/lang to complete a happy path

[LoTwT]

description

I ran pnpm create @ast-grep/lang and followed the prompted default configs, but it came across some errors.

The process was interrupted and the project codes were generated partially.

I think the Tree-sitter package to use and its default string are confusing. It's better to clarify its usage and update it with a more detailed description.

[HerringtonDarkholme]

You need to use a real tree-sitter npm package. alang is not a real programming language.

You need real programming language and has tree-sitter package.

https://github.com/ast-grep/langs/tree/main/packages/angular

For reference, you can use awk. https://www.npmjs.com/package/tree-sitter-awk

[HerringtonDarkholme]

In terms of description, #16 is tracking a doc for such usage

[LoTwT]

I know and I tried a real tree-sitter npm package. It works. Looking forward to the document. ♥️

Besides, the only little confusing thing is that when setting the language name to some-lang, the Tree-sitter package to use will show a default value tree-sitter-some-lang. It may lead users to misunderstand that it will work. Should the default value be removed?

[HerringtonDarkholme]

TBH I think this feature is only for language author or person who does already have a parser in hand. So tree-sitter-xxx is probably a good default name for them to find the package.

Besides that, I don't think ordinary user will look at this repo at all 🤣

[LoTwT]

🤣You are right.

[HerringtonDarkholme]

btw I do think the error reporting is horrendous. I will create a new issue for it

[LoTwT]

I find some new issues.

When there's no tree-sitter-cli installed globally, it will fail.

And after installing it, it came across another error

[HerringtonDarkholme]

hmm it's right, tree-sitter-cli should be in devDependencies

the other warning comes from tree-sitter cli. :/

Would you like to open an issue there?

[HerringtonDarkholme]

I pushed a new 0.0.0-prerelease to npm

[LoTwT]

hmm it's right, tree-sitter-cli should be in devDependencies

the other warning comes from tree-sitter cli. :/

Would you like to open an issue there?

You say tree-sitter-cli should be in the devDependencies. But when I run pnpm create @ast-grep/lang@latest hlang, it's in the dependencies. Is it the right place?

For the second error Failed to find tree-sitter section in package.json, unable to migrate, I don't know how to describe it in a minimum reproduction.😢

[HerringtonDarkholme]

@LoTwT thanks for reporting! devDeps is fixed. I will also investigate how to suppress the warning.

[LoTwT]

description

Hi, @HerringtonDarkholme. Today I tried pnpm create @ast-grep/lang again and failed. The error stacks are the following. It seems related to the build script. 😭

system info

➜ npx envinfo --system  --binaries --browsers

  System:
    OS: macOS 15.3.1
    CPU: (10) arm64 Apple M1 Pro
    Memory: 1.73 GB / 32.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 22.14.0 - ~/.local/state/fnm_multishells/907_1739321328392/bin/node
    Yarn: 1.22.22 - ~/.local/state/fnm_multishells/907_1739321328392/bin/yarn
    npm: 10.9.2 - ~/.local/state/fnm_multishells/907_1739321328392/bin/npm
    pnpm: 10.4.1 - ~/.local/state/fnm_multishells/907_1739321328392/bin/pnpm
    bun: 1.2.3 - ~/.bun/bin/bun
  Browsers:
    Chrome: 133.0.6943.55
    Safari: 18.3

error

[HerringtonDarkholme]

can you manually run tree-sitter build -o parser.so ?

[LoTwT]

can you manually run tree-sitter build -o parser.so ?

It works! 😱

[LoTwT]

It may related to the pnpm v10. The successful try is using the global tree-sitter-cli. It also fails after I remove it.

When I downgrade to pnpm v9, it works.

When using pnpm v10, it works after I run pnpm approve-builds and allow the scripts.

---

Another question, do these warnings matter?