![](data:image/svg+xml;charset=utf-8,<svg height="31" width="156" xmlns="http://www.w3.org/2000/svg" version="1.1"/>)
I made a very simple library which contains a .d.ts (source) which has the following structure (I omit the details because the file works fine, it likely is a config issue in my project): // Some helper types and interfaces type TranslationFunction = /* … */; export { TranslationFunction }; Then, I do npm i […]
- Tags 'build'), "$game/*": ["./src/game/*"], "$hooks/*": ["./src/hooks/*"], "$network/*": ["./src/network/*"], "$pages/*": ["./src/pages/*"], "$phaser/*": ["./src/phaser/*"], "$rematch/*": ["./src/rematch/*"], "$src/*": ["./src/*"] }, "$types/*": ["./src/types/*"], "allowSyntheticDefaultImports": true, "components/*": ["src/components/*"], "containers/*": ["src/containers/*"], "coverage"] } Finally, "es2017" ], "experimentalDecorators": true, "extendedDiagnostics": true, "helpers/*": ["src/helpers/*"], "jsx": "preserve" }, "lib": [ "dom", "module": "esnext", "moduleResolution": "node", "noImplicitAny": false, "noUnusedLocals": true, "noUnusedParameters": false, "paths": { "$common/*": ["../Common/*"], "preserveConstEnums": true, "removeComments": false, "resolveJsonModule": true, "rootDir": "../", "skipLibCheck": true, "sourceMap": true, "strict": true, "strictFunctionTypes": false, "target": "esnext" }, //"noEmit": true, baseUrl, config: config, exclude: /node_modules/, here is my tsconfig.json: { "compilerOptions": { "allowJs": true, I can hover over t in this file and it tells me that it has the proper type as defined in my original index.d.ts. This means that when I'm in, I do npm i -D embed-i18n-webpack-plugin to install the package into my own project and create a file typings/translation.d.ts to declare a gl, I get an error stating Cannot find name 't'. ts(2304) BUT if I simply comment the import inside my typings/translation.d.ts: // import { T, I have some other files declaring constants but they never import anything and work as expected. However, I have tried some things to see if that would solve my issue: Copying the content of my package's type declaration inside my typings/transla, I made a very simple library which contains a .d.ts (source) which has the following structure (I omit the details because the file works fin, I usually use them in plain TS so it works fine. It's the first time I use one inside another type declaration file. In case it might be rel, it collapses into any. Maybe the type declaration file of my package is wrong and should contain some declare module? I'm not really 100% su, it likely is a config issue in my project): // Some helper types and interfaces type TranslationFunction = /* ... */; export { Translation, it properly finds it. In this same typings directory, when I try to use the global t function inside my code