-
Notifications
You must be signed in to change notification settings - Fork 109
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Imports from '@material/...' have no available symbols #1040
Comments
adding some context here. my {
"compilerOptions": {
"declaration": true,
"importHelpers": true,
"downlevelIteration": true,
"emitDecoratorMetadata": true,
"esModuleInterop": true,
"experimentalDecorators": true,
"lib": ["es5", "es6", "dom"],
"moduleResolution": "node",
"newLine": "lf",
"noEmitOnError": false,
"noErrorTruncation": true,
"noFallthroughCasesInSwitch": true,
"noStrictGenericChecks": true,
"noUnusedLocals": true,
"noUnusedParameters": true,
"preserveConstEnums": true,
"pretty": true,
"skipLibCheck": true,
"sourceMap": true,
"strict": true,
"stripInternal": true,
"target": "es5",
"types": []
},
"exclude": [
"scripts/**/*.ts"
],
"bazelOptions": {
"workspaceName": "mdc",
"es5Mode": true,
"tsickle": true,
"tsickleGenerateExterns": true,
"tsickleExternsPath": "externs.js",
"googmodule": true
}
} |
I am pretty confused here because I'm unable locally to get code to trigger the One thing I noticed is that you are providing |
@emvar - thank you, that was super helpful. dropping that from my
This is odd, because it should be exporting that value. The originally-specified value is here in the MDC sources. Examining Bazel's intermediates on-disk, I see a lot of these files, where exports might be expected to live:
My {
"compilerOptions": {
"declaration": true,
"importHelpers": true,
"downlevelIteration": true,
"emitDecoratorMetadata": true,
"esModuleInterop": true,
"experimentalDecorators": true,
"lib": ["es5", "es6", "dom"],
"moduleResolution": "node",
"newLine": "lf",
"noEmitOnError": false,
"noErrorTruncation": true,
"noFallthroughCasesInSwitch": true,
"noStrictGenericChecks": true,
"noUnusedLocals": true,
"noUnusedParameters": true,
"preserveConstEnums": true,
"pretty": true,
"skipLibCheck": true,
"sourceMap": true,
"strict": true,
"stripInternal": true,
"target": "es6",
"types": []
},
"exclude": [
"scripts/**/*.ts"
],
"bazelOptions": {
"workspaceName": "mdc",
"tsickle": true,
"googmodule": true
}
} |
I think the issue is now imports of '@Material'. I wrote some info about how we get confused by them here: I think @alexeagle is the master of the bazel rules. Alex, do we expect this to work? |
No, I'm not sure whether this should work or not. We don't really support Closure + Bazel/TS yet, due to resources... but I'm talking to that team today about it. I'll dig into #1041 first. |
Hello esteemed
tsickle
authors,I am having trouble using
tsickle
via Bazel, to compilematerial-components-web
from its TS sources. I'm usingrules_closure
(latest, plus some patches, that shouldn't interfere here), andrules_nodejs
latest as well.Here's the output I get when trying to compile things:
Now, digging into the sources it mentions, here is the original line of TypeScript (extra lines provided for context here, last one is the offending line):
This file is picked up by
tsc
/tsickle
and rewritten into Closure-style JS, which corresponds to that set of imports (again, context provided, but the offending line is at the end):The line that's breaking the build, currently, is:
This leads to a few questions:
tsickle
?The text was updated successfully, but these errors were encountered: