This repository was archived by the owner on Feb 19, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 9
This repository was archived by the owner on Feb 19, 2020. It is now read-only.
Inconsistent generated output #70
Copy link
Copy link
Open
Description
Hi,
Given the following import statement
import { promisifyMeteorCall } from 'imports/utils/meteor';and the following tsconfig.json
{
"compilerOptions": {
"allowJs": true,
"allowSyntheticDefaultImports": true,
"alwaysStrict": true,
"baseUrl": ".",
"jsx": "react",
"lib": [
"es2017",
"dom"
],
"paths": {
"*": ["*"],
"imports/*": ["imports/*"]
},
"module": "commonjs",
"moduleResolution": "node",
"noImplicitAny": false,
"noImplicitReturns": true,
"noImplicitThis": true,
"pretty": true,
"removeComments": true,
"sourceMap": true,
"target": "es5"
},
"include": [
"client/**/*",
"server/**/*"
],
"exclude": [
"node_modules",
".meteor"
]
}An error occurs saying
Unable to resolve some modules:
"imports/utils/meteor" in /Users/ssilvestri/dev/trumid/studio/packages/ui/imports/components/Buttons/SystemRefresh.js (web.browser)What's interesting here is the generated code, for the imports look as follows:
var React = require("react");
var meteor_1 = require("imports/utils/meteor"); // <---- the outlier
var Button_1 = require("material-ui/Button");
var Dialog_1 = require("material-ui/Dialog");
var Typography_1 = require("material-ui/Typography");
var styles_1 = require("material-ui/styles");which of course makes sense, imports/utils/meteor doesn't make sense here so of course it can't resolve it. But if we look at all the other modules that have been generated from TypeScript we see this imports similar to this
var FieldComponents_1 = require("/imports/components/Form/FieldComponents");where the statement has been translated to have a / in front, which meteor understands.
Why are some being transformed into the statements with a leading slash and others not?
Metadata
Metadata
Assignees
Labels
No labels