I am seeing the same issue as you describe while doing this:

#tangle ~/.config.nvim/init.lua
@code lua
bla bla bla bla
@end

Might it be that we both stumbled upon a bug? A penny for your thoughts :-)

Could you check it with tangle: code/hello.go inside @document.meta?

This way of specifying should work, and if it does, it is probably a problem of the treesitter parser. We are currently developing a new version that should fix all the problems, so please use the document.meta method for now unfortunately.

If specifying in meta also does not work, plz report it as it probably is a bug in tangle module.

I just tried out using the document metadata and that works. i.e. it produces the file in the right directory with the expected contents.

Unfortunately, for my current use case, I don't want to tangle all code blocks of the same file type to the same file so I've "hacked" the tangle module to treat white spaces as /, so I can do something like:

#tangle code go hello.go
@code go
...
@end

I had to add the following line to the tangle module (this function) though:

-- replace white spaces with `/` for now
file = file:gsub("%s+", "/")

Go ahead and join the development of the v3 parser ;)

Haha Im not an expert on these, just have an interest. I’m still learning but if an opportunity to contribute presents itself then I’d be happy to :)

Try the hack that I did for now until the parser is fixed?

No, this kind of ability is beyond me. I mainly do C++ and Haskell. I know nothing about Lua and/or Neovim plugin development.