An Angular 2 Webpack Starter kit featuring Angular 2, Router, TypeScript, and Webpack by AngularClass
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.)
now I have to use that:
<link rel="stylesheet" type="text/css" href="node_modules/primeui/primeui-ng-all.css" />
how can I properly inject add these css files dependecies, I am new to front-end development, so sorry if its kinda newbie question
for static
my fav resource for folks new to webpack:
https://github.com/petehunt/webpack-howto
https://github.com/petehunt/webpack-howto
I miss those from 3.0 :(
I just switched out my systemJs in favor of webpack. Now I don't need system.js, rx.js, the System.config block, or the System.import statement. My index.html is so much cleaner and all the transpiling is done at build time. Isn't this the way it's supposed to be? :smile:
Hello, I'm new to angular 2 and I started with your great pack. But I don't really understand the platform folder. It seems very complicated to me. And I don't undestand why the browser folder. It doesn't seems to be releated to browser at all. I hope someone coule help me to better understand.
hey all, question on webpack's build. I've been using the convention of separate template files, and i've been putting them in the same folder as all of my typescript files. when I built the prod distribution, it stopped being able to find them, because the referenced folder doesn't exist anymore. is there an expectation that template files are going into a static folder?
@tstirrat15 I also keep my template files in the same folder. I reference them in templateUrl by name only (no path) and I use the moduleId property to specify a relative file. e.g.
See this post for more details: http://schwarty.com/2015/12/22/angular2-relative-paths-for-templateurl-and-styleurls/
moduleId: module.id,
templateUrl: 'myFile.tpl.html'See this post for more details: http://schwarty.com/2015/12/22/angular2-relative-paths-for-templateurl-and-styleurls/
I'm running into a different problem now. I updated to the most recent version of webpack, and I'm getting an error that says:
Error: Cannot resolve 'file' or 'directory' ./app in /home/tstirrat/project-gutenberg/node/src
Required in /home/tstirrat/project-gutenberg/node/src/main.browser.ts Error: Cannot resolve 'file' or 'directory' ./app in /home/tstirrat/project-gutenberg/node/src
Required in /home/tstirrat/project-gutenberg/node/src/main.browser.ts
at ResolutionError.Error (native)
at new ResolutionError (/home/tstirrat/project-gutenberg/node/node_modules/awesome-typescript-loader/dist/deps.js:281:7)
at /home/tstirrat/project-gutenberg/node/node_modules/awesome-typescript-loader/dist/deps.js:164:33
at run (/home/tstirrat/project-gutenberg/node/node_modules/core-js/modules/es6.promise.js:89:22)
at /home/tstirrat/project-gutenberg/node/node_modules/core-js/modules/es6.promise.js:102:28
at flush (/home/tstirrat/project-gutenberg/node/node_modules/core-js/modules/_microtask.js:14:5)
at nextTickCallbackWith0Args (node.js:452:9)
at process._tickCallback (node.js:381:13)But I've got app in that directory. ls output:
app assets custom-typings.d.ts index.html main.browser.ts npm-debug.log platform polyfills.ts vendor.tsAny idea what's going on?
I figured it out. It turned out that the new version relied on an index.ts, which I had deleted, thinking I didn't need it. that meant that main.ts (or whatever its current equivalent is) was trying to import from a module that wasn't well-defined (or something to that effect)
Hello, any one knows how to async load a component that has child routes.
This works:
{ path: '/about', name: 'About', loader: () => require('es6-promise!./about')('About') },But this throws an error:
{ path: '/...', name: 'Exam', loader: () => require('es6-promise!./exam')('Exam') },The error is: "Tried to get instruction before the type was loaded".
and I have few references to
.js files from vendor/ in my index.html which obviously fail because the vendor folder is never dispatched to the browser.
any idea what am I doing wrong here?
