-
Notifications
You must be signed in to change notification settings - Fork 12k
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
Webpack build system upgrade tracker #1356
Comments
I would love to help with this. Is there more detail on these action items? |
Me too. Right now, I have to mix&match angular-cli with my webpack config. I would like to help in order to get this feature released |
Hi @RobCannon and @cortopy, we already have some people assigned to these and are working on getting them done as fast as possible. I don't think more help would be helpful right now though... too many cooks in the kitchen so to say, but thank you for offering! |
Does this mean you're leaving SystemJS behind? And will you provide an upgrade route in that case through ng upgrade or similar? I've built a fairly large app with the cli now, and I'd rather not scrap it.. :3 |
@yusijs there will be an upgrade route, yes. We will document it. |
Can you tell me to load a .scss file? I see there is sass support built in and I am able to get .scss files to process for individual components, but I can't figure out how to load a master style for the whole web app. |
3 off the list thanks to #1359 |
@RobCannon there is no such functionality present in |
@filipesilva, @TheLarkInn: We're punting lazy loading until the webpack branch makes it to master. It's a difficult problem with many moving pieces and we will need a proper prototyping and design phase to solve it. |
Great work @filipesilva and @TheLarkInn. I can confirm SCSS is working out of the box with |
@tapas4java broken? How? Tell me more. It's working in our tests. Did you run |
@filipesilva I have created new project and ran
|
@tapas4java looks like missing dependencies. Did you |
Thanks @filipesilva ....After
|
Is this the only command that fails like this? |
@tapas4java can you show me your |
@tapas4java fixed in #1387 |
Thanks @filipesilva,
Getting below error in browser console:
|
@filipesilva I have a feature branch on my local that fixes this one specific feature. I just need to run tests and then setup a PR. If not today tomorrow for sure. |
(That.is the host) we just need to set the host flag so 1. It defaults to 'localhost' and like above, set commandOptions.host to replace anywhere is serve.ts where |
@TheLarkInn Thinking more about it I don't think that a |
@filipesilva @TheLarkInn Do you think webpack branch is ready to be used. I know this branch is not stable enough, which is OK. Apart from stability and minor new features, are there any major changes planned? Also how do I use global SASS files with this branch? |
@mmrath this branch is not ready to be used. It is still under active development and we give no guarantees over what might or might not be changed. Until it goes into master it's not the official branch and there should be no expectation of support being given for it. |
@filipesilva Thanks for your reply. WARNING in ./ |
When I create a new project |
Adding a question (from #1436) about fonts: Can the web pack config handle fonts from third party libs like Bootstrap in a generic way, or should there be a way for the user to specify a custom configuration for things like this? Or perhaps is this just something the developer needs to configure properly in their project? Somewhat of a web pack newbie, apologies if this seems like a basic question :) |
@mmrath I have not seen that error happen, no. Can you give me some reproduction steps so I can try to debug it? |
@filipesilva It happens with angularfire2 as well, see: angular/angularfire#376. |
So it's a typescript problem? Hm, odd. @TheLarkInn I guess we can update to TS2.0? I'd still like to know more about the issue and how to reproduce it... |
@filipesilva I'm pretty sure as well that TS2.0 has nothing to do with it. The main problem is the generated sourcemap files referencing to non-existent source files. Adding |
@filipesilva A sample repo located at https://github.com/mmrath/ng-cli-webpack-test . Please let me know if you are able to reproduce the issue with repo. |
Periscope also uses Angularfire2, and does not compile. Output: https://gist.github.com/hansl/7b53915bfaa55d72ebe842807b0351e4 |
@Brocco I couldn't repro the
We also test for git on our e2e test suite, which makes me think your scenario must have been a fluke (or something we're not testing for). |
Hello everyone, Since we don't use separate typings for You can see a sample error here. I have also added to it some steps that can be used to separate the typings manually so that you don't get this error. Does it make sense to separate the typings for (maybe via different tsconfig and types as mentioned in #1449?) Thanks! |
Hi. |
Just out of curiosity @jvbianchi can you try |
@TheLarkInn I tried |
Thanks everyone. This issue is now closed as the WebPack branch is merged. If you have build issues, please create separate issues on github instead of refering to this. A NPM package will be published sometime this week with this. It will use a separate I want to specially thank @TheLarkInn and @filipesilva for their work on this. Without you, it's clear we'd still be using Broccoli. Good work to both of you! |
Can't wait for this to hit npm! Hoping the upgrade path is ready to by then! :) |
Was there a conclusion about the convention for global css? |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Remaining action items:
require
from test shim fix: fixes for path mappings, tests, and coverage #1359figure out lazy loading--source-dir
support fix(build): re-add support for sourceDir #1378prod
target #1395ng e2e
test using prod builds chore(tests): add prod env e2e test #1394libs
option intsconfig.json
fix: update to awesome-typescript-loader 2.1.0 #1425module.id
chore(blueprints): remove module.id #1426ng serve
feat: add host flag support for ng serve #1442Things to investigate:
The text was updated successfully, but these errors were encountered: