Jeff Lu

I have a similar issue. I cloned the project, ran npm install then npm run integration. npm ERR! code ENOLOCAL npm ERR! Could not install from "../dist" as it does...

@SebastianSchenk I got it working, make sure you specify your moduleName under rollup:umd If you are running the latest rollup it should be "name": "you-module-name"

I'm getting these errors when npm run roll & npm run roll:prerender ▁ Building...✖ Compile error: Error: Error encountered resolving symbol values statically. Could not resolve events relative to /Users/ljeff/git_repo/sandbox/angular/angular-rollup-starter/node_modules/@types/chokidar/index.d.ts.,...

removing @types/chokida and/or "chokidar": "^1.6.1", ▁ Building...✖ Compile error: Error: Error at /Users/ljeff/git_repo/sandbox/angular/angular-rollup-starter/node_modules/@types/browser-sync/index.d.ts:6:1: Cannot find type definition file for 'chokidar'. Error at /Users/ljeff/git_repo/sandbox/angular/angular-rollup-starter/node_modules/@types/lodash/index.d.ts:12898:29: Cannot find name 'object'. Error at /Users/ljeff/git_repo/sandbox/angular/angular-rollup-starter/node_modules/@types/lodash/index.d.ts:19638:15:...

hmm. I have done that several times. Same errors. I think this will work great with my next project if I can get it running with Angular 4. Can you...

Thanks @jkur, I'm looking at https://github.com/bleenco/angular-webpack-seed, I ran npm run build:prod, can you explains what 0.app.bundle.js, 0.server.js & server.js are for since the app will run with just app.bundle.js?

+1 either solution will be beneficial and vital for us to move forward.

@agrueneberg still getting the same error with your suggestion ``` app.use(corser.create({ endPreflightRequests: false, requestHeaders: corser.simpleRequestHeaders.concat(["Content-Type"]) })); Header Response access-control-allow-credentials:false access-control-allow-headers:* access-control-allow-methods:GET,POST,OPTIONS access-control-allow-origin:* access-control-max-age:86400 cache-control:private, max-age=300 content-length:2 ```

Yes, it's Chrome Version 61.0.3163.91 (Official Build) (64-bit) The express is fronted by Akamai. Seems whatever I do on express it has no effect. The question is if access-control-allow-headers:* why...

This is the request Request URL:https://stage.mydomain.com/web-pwa/query Request Method:OPTIONS Status Code:200 Remote Address:xxx.xxx.xxx.xxx:443 Referrer Policy:no-referrer-when-downgrade request header :authority:stage.mydomain.com :method:OPTIONS :path:/web-pwa/query :scheme:https accept:*/* accept-encoding:gzip, deflate, br accept-language:en-US,en;q=0.8 access-control-request-headers:content-type access-control-request-method:POST cache-control:no-cache origin:https://dev.weather.com pragma:no-cache...