EclipseFdn / EclipseFdn/publish-extensions

Missing `/out` directory in template-string-converter

Open
#522 2 comments 0 reactions 0 assignees View on GitHub
bug team: IDE
Dominant language
JavaScript
Stars
341
Forks
428
Avg merge
40m
Merged PRs (30d)
2

Description

**TL;DR;**
In `template-string-converter` extension's directory the `/out` folder is missing.

When I've installed `template-string-converter` in Code OSS (from Arch official repo) which by default uses OpenVSX registry the `/out` directory is missing in extension folder, which prevents it from being activated. Since VisualStudio Marketplace version doesn't have such a problem, and extension maintainer doesn't seem aware of OpenVSX existance, I suppose this issue belongs here. ¯\\\_(ツ)_/¯ Full story described in meganrogge/template-string-converter#59.

Maybe related to #163.

Contributor guide

Open the contributing guide

Research direction

Inspect the publishing path for the template-string-converter extension and compare the OpenVSX package with the Visual Studio Marketplace version, using the missing /out directory as the starting symptom. Determine where the published artifact loses /out, then verify that the resulting package contains it and activates in Code OSS.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, vscode
Domain
release
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.