TypeScript Files Importing 'Path' Where There is No 'Path' Package

Question

I have been working with Angular Universal for a couple of weeks and I have noticed that many instances of Angular Universal have a server.ts document that is located at the root directory.

This server.ts file imports several TypeScript installations which are usually available from a /typings directory. However, there is one import library that always triggers an error when editing in the Atom IDE and disallows me to compile the file, only emit it:

import * as path from 'path';

Up until now, I have yet to figure out exactly where this 'Path' library is derived from. I have tried to install it using TypeScript itself:

typings install path

and I receive the following error:

typings ERR! message Unable to find "path" ("npm") in the registry.

Anyone familiar with this 'path' import reference and exactly where it is coming from?

Thanks.

slaesh · Accepted Answer · 2016-09-22 17:40:43Z

1

path is a part of node.

So typings install node is the key! :)

https://github.com/DefinitelyTyped/DefinitelyTyped/blob/master/node/node.d.ts#L2261

answered Sep 22, 2016 at 17:40

slaesh

17k6 gold badges53 silver badges54 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

Mindsect Team Over a year ago

Thanks a million! Ask and ye shall receive an answer to your liking :-)

Collectives™ on Stack Overflow

TypeScript Files Importing 'Path' Where There is No 'Path' Package

1 Answer 1

1 Comment

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

1 Comment

Your Answer

Sign up or log in

Post as a guest

Related