An Angular 2 Webpack Starter kit featuring Angular 2, Router, TypeScript, and Webpack by AngularClass
Are there examples of how to add a .js based project to starter? Something like primeng? When I add the typings file to tsconfig.json but during compile I get a bunch of warnings like:
WARNING in ./~/primeng/components/datagrid/datagrid.js
Cannot find source file 'datagrid.ts': Error: Cannot resolve 'file' or 'directory' ./datagrid.ts in /Users/nsmith/projects/cohortable/node_modules/primeng/components/datagrid
so, with 4.0.0, what providers go here https://github.com/AngularClass/angular2-webpack-starter/blob/master/src/main.browser.ts only angular2’s, or 3rd party as well
it’s little confusing
oups, the first link was supposed to be https://github.com/AngularClass/angular2-webpack-starter/blob/master/src/platform/browser/providers.ts
then there is the file that just bootstraps the stuff from the browser platform
but if you have providers for example a web worker you might want to bootstrap that with some other platform dependancies.
yea, but I’m still not sure what belongs where, according to this https://github.com/AngularClass/angular2-webpack-starter/issues/454#issuecomment-199421596 only angular/vendor stuff belongs there
but
he’s putting there this as well https://github.com/AngularClass/angular2-webpack-starter/blob/master/src/platform/browser/directives.ts#L32
also I have some vendor providers that require some of my code(ngrx/store
providerStore requires my reducers).. so where should that go?
the same code also works fine when in a JSPM based build
This message was deleted
anyone around that can give me any suggestions on how to fix? started a week or so ago when I upgraded from around the beta.8 versions. In the mean time I've tried starting from a fresh copy of the starter, it'll work fine for a while but eventually it'll fail on that error. Sometimes it'll fail after just adding a new <div> to an HTML template
eventually the error is on this line: modules[moduleId].call(module.exports, module, module.exports, hotCreateRequire(moduleId));
it errors out before it gets to any code in main.browser.ts so it seems likely that it has nothing to do with any angular code
[Error] Runtime error: reflect-metadata shim is required when using class decorators
and get library reference errors ... the exports in ng2-Translate are not resolved properly
'ng2-translate/src/translate.service.d.ts';
WARNING in ./~/ng2-translate/ng2-translate.js
Cannot find source file 'ng2-translate.ts': Error: Cannot resolve 'file' or 'directory' ./ng2-translate.ts in C:\src\ang
ular2-webpack-starter\node_modules\ng2-translate
Cannot find source file 'ng2-translate.ts': Error: Cannot resolve 'file' or 'directory' ./ng2-translate.ts in C:\src\ang
ular2-webpack-starter\node_modules\ng2-translate
Hi everyone. I tried to upgrade to the latest version ( so to angular2-webpack-starter#4.0.0 from #0.0.0 :) ) and to merge my robust ng2 project into it (mostly app folder files), but for some reason none of my src/*/.ts files are delivered to the browser (webpack://) other than main.browser.ts, polyfils.ts & vendors.ts. And I’m gettinig polyfills.bundle.js:51 Uncaught TypeError: Cannot read property 'call' of undefined (due to previously mentioned issue I guess). Does anyone has any idea where to look @ cause I’m a bit stucked atm...
I got it! It has to do W the fact that I’ve tried changing the port from 3000 manually within webpack.dev.js.
It seems that W latest version of angular2-webpack-starter app isn’t working when starting it W none of below (which was working in previous versions):
PORT=XXXX npm start
PORT=XXXX npm run-script server:prodDid anyone had any success W running app on different port?
This message was deleted
the only thing that fixed it for me is removing the 'vendor' script from webpack as detailed in the issue thread
I did add relevant file extensions to the regexp of CompressionPlugin, and that was having the .js already anyway, but it did not help.
Howdy Yall!!!
Does anybody here use Webpack &/| Browserify and can help a brother out?
I have a browserify bundled code that I would like to wrap with webpack or alternatively bundle in webpack and return an object.
(It's a whole project on it's own)
I tried to bundle it as a library but couldn't get that one final return value.
Any thoughts?
@syberpunk I feel like the "right way TM" to use webpack is to let it bundle all the raw code, and not feed it pre-processed/bundled code. (It usually yells on the console if you do.) These like de-duping of shared dependencies can't be done if you pre-bundle the other project. (Sorry that's just advice and not technical help; that's about all I know.)
