Hey! Great job!

[BusinessDuck]

Happy to see this project on github its a really nice development direction.

I have couple of ideas for you and your team:

• Be in touch with https://www.pinecoders.com/ they can help with anything and also contribute
• Split the syntax parser (transpiler) to separate package, its might be user for VSCode plugins or any other tools, and probably pine AST transpiler might be a separated and big project. Also its a good practice to split projects to several packages.
• Please use Pine Script® instead of Pine Script™ details here, also you can check everything what is regulated by law.

[alaa-eddine]

Hey @BusinessDuck
Thank you for your message!

I'm already in touch with some Pine Script developers to get permissions for releasing ports of their indicators, and pinecoders.com is definitely on my list too 🙂.

Regarding the transpiler, this version (as mentioned in the top comment of the file) is more of a MVP that I used to bootstrap the project and begin porting the Pine Script API. A full refactor of the transpiler is planned. but my initial goal is to have enough coverage for PinceScript syntax that allows porting most of the indicators.

Compiling actual Pine Script directly to JavaScript is a long-term goal for the project. In the short term, an AI-powered converter will serve as an intermediate solution.

Regarding Pine Script® vs. Pine Script™, the official TradingView documentation (and even pinecoders.com) uses Pine Script™. Before publishing this code, I reached out to the TradingView team and got their green light to ensure that there are no intellectual property issues.

Thanks again for your message and valuable advice!

[arose26]

Hi @alaa-eddine you're probably already aware of this project but Pynescript maps Pine Script pretty reliably into python AST. Obviously there's a difference between python AST and javascript AST but it might provide some initial clues at least for getting rid of the need for 'const' and allowing pine for loop syntax, etc.

[alaa-eddine]

Hi @arose26 , yes I'm aware of this one, actually, I tried to use the provided antlr grammar files to generate the AST in javascript but it failed at some point. I did not spend too much time on it because that was not the main goal of PineTS

But I will certainly use it in the future, in fact, I'm considering to provide a transpiler that converts Pine Script code into PineTS code in order to execute it with PineTS runtime.

Parsing alone is not sufficient to run codes like Pine Script because they are domain specific and their structures, variables, and paradigms are not directly transposable to something like javascript or python.

[arose26]

I actually made some inroads on this. For now just handles the demos but wouldn't be hard to expand on.
Pine Script to PineTS
The initial pynescript dump is very time consuming, which makes it a little less useful, but at least the rest is instantaneous. Perhaps the pynescript dump could be optimized somehow too.

[arose26]

Okay I made a direct transpiler ... probably would have been faster to do this from the start haha
Pine2PineTS

[alaa-eddine]

Oh that's pretty cool, and I'm happy that PineTS is helping you.
I'll add a link in the readme file to your code so that people who want a transpiler can use your solution for now.

[arose26]

After many hours banging my head against it, I can see why you abandoned the transpilation now. The nested indents really make the grammar parser confused. However, I finally employed a preprocessing trick by automatically inserting explicit endfor and endfunction etc and it seems to support most of Pine's nastiness now.

[alaa-eddine]

@arose26 if you are willing to take the transpiler challenge, another approach to consider is using regular expressions.
one of the tracks that I explored too was to use an idea from a PineScript syntax plugin for VSCode (I forgot the name but you can certainly find it) ... it uses regular expressions to parse PineScript structures. the idea that I considered is to use these regular expressions to split the code into simpler chunks, then use a simpler ANTLR grammar to parse them.

[I-Mortals]

@alaa-eddine Can PineTS be used to add custom indicators to tradingview/charting-library? Tradingview/charting-library cannot use pine script directly.

[alaa-eddine]

@I-Mortals not natively because the official charting library does not support pine script directly as you mentioned.

but you can use PineTS to generate the values, and then render them using tradingview lightweight library (or other charting libraries)

there are some demos in the doc that use the above approach, here is one of them https://alaa-eddine.github.io/PineTS/indicators/willvixfix/index.html

in the source code of this HTML page, at the very bottom you have two scripts :

• WillVixFix.js : this one uses PineTS to get the BTC candles and calculate the indicator data and return the values
• chart.js : this one uses tradingview lite library to render the BTC chart and the indicator chart

btw : this was one of the motivations to implement pineTS, lack of support for pinescript in the front library is very limitting

[wallneradam]

Really interesting to see the progress here — especially around the grammar and AST challenges.
We ran into the exact same issues when trying to build a Pine-to-Python toolchain: nested if logic, var, delayed outputs, series structure… it quickly becomes unmanageable without a dedicated runtime.

That’s why we ended up creating two things:

• https://pynecore.org – a Python runtime that reproduces Pine’s behavior (bar-by-bar, series, var, etc.), it is open-source.
• https://pynesys.io – a compiler service, that parses Pine v6 and emits native Python code that runs on PyneCore

It’s pure Python, and matches TradingView results bit-for-bit.
Just thought I’d share in case this helps others navigating similar problems around AST and execution models!

[arose26]

Really interesting work @wallneradam. After spending much effort on tests revolving around that, I can appreciate the magnitude of your results!