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
Strategie Import Specifier to Uri Map. aka loader.input = MapObject
code-oss has references to 'loader!./' Uri specifications
code-oss has references to 'vs/'
code-oss has references to 'vs/.json'
code-oss has loaders in ./src/.js src/vs/.js src/vs/*.ts the main loader is a extra repo called vscode-loader
map rules by file structure is possible with relative pathes as we lookup pathes anyway we can specifie vs/css!./ alwaysrelativ as specifier as it looks like it is always relativ used also vs/* needs only mappings to the .ts extension
also remember that the product.json methods get deprecated: by vscode-build/repos/code-oss-dev/src/vs/platform/product/common/productService.ts
Found a Related issue
We can simply drop the vscode-loader adoption as they drop that dept them self. anyway we will Execute more fast so we do so but we will throw away loader compat for the build process......
migrate.js in the new build we should replace that with out build process as we are able to implement that directly into our loader we do not need to copy files around.
The text was updated successfully, but these errors were encountered:
Strategie Import Specifier to Uri Map. aka loader.input = MapObject
code-oss has references to 'loader!./' Uri specifications
code-oss has references to 'vs/'
code-oss has references to 'vs/.json'
code-oss has loaders in ./src/.js src/vs/.js src/vs/*.ts the main loader is a extra repo called vscode-loader
map rules by file structure is possible with relative pathes as we lookup pathes anyway we can specifie vs/css!./ alwaysrelativ as specifier as it looks like it is always relativ used also vs/* needs only mappings to the .ts extension
also remember that the product.json methods get deprecated: by vscode-build/repos/code-oss-dev/src/vs/platform/product/common/productService.ts
Found a Related issue
We can simply drop the vscode-loader adoption as they drop that dept them self. anyway we will Execute more fast so we do so but we will throw away loader compat for the build process......
The text was updated successfully, but these errors were encountered: