microsoft / microsoft/TypeScript
TSC fails to emit required files when run below node_modules
Nadie ha tomado este issue todavía.
- Lenguaje dominante
- Go
- Estrellas
- 111k
- Forks
- 14.3k
- Merge medio
- 2 d 4 h
- PR fusionados (30 d)
- 132
Descripción
TypeScript Version: 3.2.0-dev.20181107
Search Terms: node_modules
Code
/tmp/node_modules/tsc-test/tsconfig.json
{
"compilerOptions": {
"outDir": "dist"
},
"files": [
"src/index.ts"
]
}
/tmp/node_modules/tsc-test/src/index.ts
import { A } from './A';
export const main = () => {
console.log('A=', A);
};
/tmp/node_modules/tsc-test/src/A.ts
export const A = 'A';
Expected behavior:
Output files:
/tmp/node_modules/tsc-test/dist/index.js/tmp/node_modules/tsc-test/dist/A.js
Actual behavior:
Output files:
/tmp/node_modules/tsc-test/dist/index.js
"use strict";
exports.__esModule = true;
var A_1 = require("./A");
exports.main = function () {
console.log('A=', A_1.A);
};
No A.js is output
Notes:
I wanted to build a typescript project as part of an npm postinstall script, to enable installation from npm or from git. In the case of installation from npmjs, dist/ will already exist. In the case of installation from git, dist/ will be missing and build will be run.
After setting this up, I noticed that only files listed in my tsconfig files list were being emitted when installing from git. I looked around for tsconfig or tsc options that may change this behavior, but realized it probably had to do with 'node_modules' being in the path.
I debugged the issue by modifying the built tsc.js. In my case, the problematic code is in nodeModuleNameResolverWorker/tryResolve, specifically here:
const { path: candidate, parts } = normalizePathAndParts(combinePaths(containingDirectory, moduleName));
const resolved = nodeLoadModuleByRelativeName(extensions, candidate, /*onlyRecordFailures*/ false, state, /*considerPackageJson*/ true);
// Treat explicit "node_modules" import as an external library import.
return resolved && toSearchResult({ resolved, isExternalLibraryImport: contains(parts, "node_modules") });
The call to contains(parts, "node_modules") should likely consider the project root directory, and ignore "node_modules" in the path parts above the root.
Guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Línea de trabajo
Comienza en src/compiler/moduleNameResolver.ts, en nodeModuleNameResolverWorker/tryResolve, especialmente en la lógica de contains(parts, "node_modules") descrita en el issue. Reproduce el proyecto proporcionado /tmp/node_modules/tsc-test con TypeScript 3.2.0-dev.20181107 y compara los archivos generados. Se considera terminado cuando la compilación genera tanto dist/index.js como dist/A.js cuando el proyecto está debajo de node_modules.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- typescript
- Área
- compilers
- Tipo de issue
- Error
- Dificultad
- 3/5
- Tiempo estimado
- 1-2 días
- Estado de actividad
- Estancado
- Claridad
- Bien especificado
- Aptitud para principiantes
- 35/100