Babel cannot parse decorators

[lazarljubenovic]

We're getting the following error on our codebase.

Babel couldn't parse file in @webdoc/parser (libs/...component.ts)
C:\...\nvm\v15.4.0\node_modules\@webdoc\cli\node_modules\@babel\parser\lib\index.js:748
    const err = new SyntaxError(message);
                ^
SyntaxError: This experimental syntax requires enabling one of the following parser plugin(s): 'decorators-legacy, decorators' (11:0)

Obviously, the babel parser is missing the decorators and/or decorators-legacy plugin, but I can't figure out how to influence the used babel plugins.

I've checked out source code for @webdoc/parser and saw the babel config file.

webdoc/packages/webdoc-parser/babel.config.json

Line 2 in 1413c09

"presets": [ "@webdoc/babel-preset" ]

But I don't see any way to influence this, so I'm not sure if this issue is a simple question or missing docs or missing feature 😄

[ShukantPal]

@lazarljubenovic I see you're interested in the source a little bit. The babel config you pointed here was for @webdoc/parser's build - not the runtime parsing of the documented codebase. Those plugins are defined here:

webdoc/packages/webdoc-parser/src/symbols-babel/index.js

Line 13 in 1413c09

const defaultPreset = [

Right now, the configuration doesn't have an option to add/remove these. The idea was to add all the plugins b/c I didn't foresee any reason not to have a plugin. I did forget decorators.

I'll try to make a fix for this tonight or tomorrow and do a quick release.

[lazarljubenovic]

The babel config you pointed here was for @webdoc/parser's build

Duh, that's obvious now. A brainfart on my part 😅 Thanks for pointing to the right direction.

I didn't foresee any reason not to have a plugin

Indeed, given the backward compatibility, I don't see why anyone would want to remove a plugin, either.

Adding plugins, on the other hand, is probably something that someone else would eventually ask for -- some people like to add all sorts of stage 1 stuff into their projects -- so that might be a good low-priority addition for the roadmap.