Izhaki

OK. Have made some progress (with some help from this [SO answer](http://stackoverflow.com/a/37309849/1179377)). If I just: npm install bezier-js --save-dev Add `bezier-js.d.ts`: ``` declare module 'bezier-js' { export = class Bezier...

@danmarshall If I use my (4 lines) `bezier-js.d.ts`, which was used without the `@types/bezier-js`, then obviously not. But I can simply copy the content of https://github.com/DefinitelyTyped/DefinitelyTyped/blob/types-2.0/bezier-js/index.d.ts (without the namespace) to...

OK, just to confirm. npm install bezier-js @types/bezier-js --save-dev then if I manually edit `node_modules/@types/bezier-js/index.d.ts` to the file below. It complies and run, and works with Intellisense (so long you...

@alexjlockwood In the interim, have a look how I got it working: https://github.com/Izhaki/gefri/blob/master/src/view/viewees/visibles/path/bezier-js.d.ts

@danmarshall Sure. But will need to find a bit of time (to test it all).

@vjonas Can you share the import clause?

There could be a few issues here. First, it appears you run the command from the sub-package folder, so babel may see `./` (root) as the folder you are running...

Well if you do this: ``` [ "module-resolver", { root: 'xxxxxxxxxxxxxxxxxxxx', alias: { "@package1": "../package-1" } } ] ``` It does pickup `package-1`, which suggests that the `root` property is...

Note that this works: ``` "module-resolver", { resolvePath(sourcePath) { switch (sourcePath) { case "@package1": return path.resolve(__dirname, "packages/package-1"); default: console.log(sourcePath); } } } ```

@tleunen I think there's an issue with the plugin: It doesn't resolve the root correctly when using `babel.config.js` which is central to mono-repos with babel 7 ([docs](https://babeljs.io/docs/en/config-files#root-babelconfigjs-files)).