You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Trying to add Vue Language-Tools for the default block parsers that ships with Vue, but it seems to make use of optional chaining and nullish coalescing operators, which throws errors on build.
To Reproduce
Steps to reproduce the behavior:
Build my feature fork or load any library using optional chaining or nullish coalescing: josh-hemphill/astexplorer
See error
The full error:
ERROR in ./node_modules/@vue/language-core/lib/virtualFile/computedSfc.js 14:107Module parse failed: Unexpected token (14:107)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
| return res;
| };
> const template = computedNullableSfcBlock('template', 'html', (0, computeds_1.computed)(() => parsed()?.descriptor.template ?? undefined), (_block, base) => {
| const compiledAst = computedTemplateAst(base);
| return mergeObject(base, {
@ ./src/parsers/vue/vue-language-tools-core.js 26:4-37:6@ ./src/parsers sync ^\.\/(?!utils|transpilers)[^/]+\/(transformers\/([^/]+)\/)?(codeExample\.txt|[^/]+?\.js)$
@ ./src/parsers/index.js
@ ./src/store/reducers.js
@ ./src/app.js
The text was updated successfully, but these errors were encountered:
Just to voice I'm trying to build some stuff using optional chaining too and it means I can't easily switch between coding the babel plugin and testing it in AST Explorer which is a shame as it's so incredibly useful. So I'd also appreciate support for these.
Describe the bug
Trying to add Vue Language-Tools for the default block parsers that ships with Vue, but it seems to make use of optional chaining and nullish coalescing operators, which throws errors on build.
To Reproduce
Steps to reproduce the behavior:
The full error:
The text was updated successfully, but these errors were encountered: