-
Notifications
You must be signed in to change notification settings - Fork 10
App first launch failure #14
Comments
I am getting the same issue and cannot proceed since i am using "ng build && node server.js" |
@Kunal1985 after taking a second look at my stack trace above, if you are having similar errors it looks like TypeScript definition mis-matching within certain Class constructors. I'll check with our TS guys and report back. |
@Kunal1985 reference: Esri/jsapi-resources#77 (comment). I was able to make the following quick/rough changes and got the app running. It had a few other minor TypeScript errors that didn't seem to affect the compiler. Hopefully between the comment reference and my snippets below you can get it going. We'll take a closer look at updating the repo and giving it a more thorough vetting on this issue. With the Synced 3D Views sample try making the following changes in // STEP 1.B
// create a graphic to display the new unioned buffer geometry
var bufferGraphic = new Graphic({
geometry: bufferGeometry,
symbol: new SimpleFillSymbol({
color: [227, 139, 79, 0.7] as any as __esri.Color,
outline: new SimpleLineSymbol({
color: [255, 255, 255] as any as __esri.Color,
width: 1
})
})
});
// STEP 2.B
// create a graphic to display the new convex hull geometry
var convexHullGraphic = new Graphic({
geometry: convexHullGeometry,
symbol: new SimpleFillSymbol({
color: [255, 255, 255, 0] as any as __esri.Color,
outline: new SimpleLineSymbol({
color: [255, 255, 255] as any as __esri.Color,
width: 2
})
})
}); And for the Geometry Engine sample in @Injectable()
export class AnalysisMapService {
map: any = null;
constructor() {
this.map = new Map({
basemap: 'dark-gray',
layers: [
new GraphicsLayer({
id: 'analysisLayer'
}),
new FeatureLayer({
url: 'http://services.arcgis.com/BG6nSlhZSAWtExvp/arcgis/rest/services/World_Volcanoes/FeatureServer/0',
id: 'volcanoesLayer'
})
] as any as Collection
});
}
} |
Not sure why but when I first ran
npm start
I got the following errors. But, after I reloaded the app manually in the browser everything worked okay after that.I'm just documenting it here in case anyone else has the same issue.
The text was updated successfully, but these errors were encountered: