Urigo/angular-meteor

[examples/AngularCLI]: "cannot find" messages as building the api server but it runs fine

atao60 opened this issue · 4 comments

atao60 commented
  • A descriptive title
  • An isolated way to reproduce the behavior (example: GitHub repository with code isolated to the issue that anyone can clone to observe the problem)
  • What version of angular-meteor you're using, and the platform(s) you're running it on
  • What packages or other dependencies you're using
  • The behavior you expect to see, and the actual behavior

See demo on github: https://github.com/atao60/angular-meteor-example-AngularCLI

The installation is described in detail in the file HISTORY

Pre-condition, main points:

During the build of the api server (Meteor), error messages are thrown for any node or meteor global reférences, eg:

server/fixtures/data.fixture.ts (1, 16): Cannot find module 'fs'.
server/fixtures/data.fixture.ts (2, 11): Cannot find name 'Assets'.

But everything runs fine...

I haven't find any workaround to avoid those messages.

ardatan commented

They are related to @types/meteor package, and probably fixed by DefinitelyTyped/DefinitelyTyped#28064
It is not directly related to angular-meteor.
Thank you for your notice!

atao60 commented

They are related to @types/meteor

Even for 'fs' and other modules provided by node?

ardatan commented

fs is provided by @types/node.

atao60 commented

Both packages @types/node and @types/meteor are referenced in package.json.

So it's quite strange that references to Meteor's Assets or most of the node's modules (fs, console, path, ... but not process!) will generate a message 'cannot find' during the Meteor phase "TypeScript Files Compilation".