TSC Does Not Run On Path To TSConfig.JSON Synced To SharePoint Library #142479
Labels
*duplicate
Issue identified as a duplicate of another issue(s)
tasks
Task system issues
typescript
Typescript support issues
Issue Type: Bug
Issue: when attempting to build (transpile) JS files from TS files using
tsc
on atsconfig.json
file whose path is created by a sync to a SharePoint document library (folder) via OneDrive, the following terminal output is observed:The path-to-
tsconfig.json
file is as follows:•
d:\dev\SharePoint\SPOSite
is the attachment point for sync of the SharePoint document library via OneDrive•
<SP-tenant-name>
is the obscured name of the tenant nameXXXX.sharepoint.com
where XXXX =<SP-tenant-name>
. This naming action for the path element is done by OneDrive syncing process.• The
<SP-site-name> - <SP-library-name>
path element is the obscured names of the site (actual name: 'mhteam') and the document library (actual name: 'SP Tools'). This naming action is done by OneDrive syncing process.Renaming the path elements associated with/created by OneDrive syncing is not possible.
Note the path-to-tsconfig.json argument enclosed by single quotes, which would be assumed to prevent the TS compiler from interpreting space characters as separate arguments and the hyphen character as designating an option (argument) to the application.
• Question posted on sharepoint.stackexchange.com with this issue went unanswered after 3 days: https://sharepoint.stackexchange.com/questions/300261/can-path-to-tsconfig-json-for-vs-code-be-to-synced-sharepoint-document-library
• VSCode started with option --disable-extensions temporarily shows same error: would presume this is not caused by any extension.
• GitHub issues filter setting 'is:issue is:open tsc' shows 42 open, 954 closed. The 42 open issues do not describe this issue.
• GitHub issues filter setting 'is:issue sharepoint' show 3 open (no relevance), 468 closed (too many to inspect)
• GitHub issues filter setting 'is:issue sharepoint sync' show 0 open, 7 closed (no relevance)
• the SharePoint subscription is an M365 E5 Developer account
Steps to reproduce:
tsconfig.json
is without defect, and drag-n-drop upload to the SharePoint document library to root level folder or containing subfolder. Check that the working tree has been copied for all files.C:\Users\username\...
with the option of the user directing to another location in the filesystem. In the present case, the attachment point was tod:\dev\SharePoint\SPOSite
, a path created for that attachment point.Version: 1.64.0 (user setup)
Commit: 5554b12
Date: 2022-02-03T04:22:20.678Z
Electron: 13.5.2
Chromium: 91.0.4472.164
Node.js: 14.16.0
V8: 9.1.269.39-electron.0
OS: Windows_NT x64 10.0.22000
VS Code version: Code 1.64.0 (5554b12, 2022-02-03T04:22:20.678Z)
OS version: Windows_NT x64 10.0.22000
Restricted Mode: No
System Info
gpu_compositing: enabled
multiple_raster_threads: enabled_on
oop_rasterization: enabled
opengl: enabled_on
rasterization: enabled
skia_renderer: enabled_on
video_decode: enabled
vulkan: disabled_off
webgl: enabled
webgl2: enabled
Extensions (25)
(1 theme extensions excluded)
A/B Experiments
The text was updated successfully, but these errors were encountered: