-
Notifications
You must be signed in to change notification settings - Fork 39
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
Add final step for building and testing in non-Dartium browsers #39
Comments
I just read Chapter 7: Production Deployment. I can't imagine someone with only 1 or 2 hours of Dart practice to dive into this part. It's really for Dart masters ! For instance :
I can add a last part for the ShadowDom polyfill but I'll be happy to skip the generation section if possible. |
I totally understand, chapter 7 is like voodoo. :) Developers shouldn't have to do half of those steps. What about just telling developers about I've also opened dart-archive/angular.dart#475 to ask that we don't need to manually add shadow_dom. cc @kathyw for her thoughts. |
Can we close this one ? |
We can't close it yet. We need a Step 9: building and testing in browsers. Topics:
As far as I could tell, the code lab doesn't show you how the app works in other browsers. Thanks! |
Hi, |
About the last topic : since ShadowDom polyfill is here from step-1. At any step we can use Run as Javascript (in my case the browser used is FF ). You can also paste the url in an other browser. I agree on import 'dart:io';
import 'package:http_server/http_server.dart';
void main() {
HttpServer.bind(InternetAddress.ANY_IP_V4, 8080).then((server) {
new VirtualDirectory('../build/web').serve(server);
});
} |
I like it. |
pub build should now work for steps 1 - 9 Can we add this as a final step? Up to you if you want to involve the Dart HTTP server. That part is optional :) |
Can you add a final step for how to build the app and open in Firefox, safari, etc ?
Thanks!
The text was updated successfully, but these errors were encountered: