Giter VIP home page Giter VIP logo

angular-webpack-cookbook's People

Contributors

dmachat avatar phisherman avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

angular-webpack-cookbook's Issues

We love your old GitBook site!

Hello @dmachat (and cc @christianmalek)! Addison here from GitBook 😄

It seems like it's been a little bit, but I recently came across your old GitBook project—http://dmachat.github.io/angular-webpack-cookbook/

I don't know the last time you checked out GitBook, but we've updated the product quite a bit from the version you were last using, and have added a suite of new features to help you customize, organize, and make overall more interactive and engaging sites in GitBook.

I'm reaching out because I'm working on a new project this month, where we'll be launching a new landing page on our homepage that showcases some of the different content that can be made on GitBook, and I think the content you've made would be perfect to feature for the initial launch.

The only thing is, that we're only aiming to include content that's on the latest version of GitBook, so it would be great to work with you on migrating it over.

Luckily, we have a tool in place that will automatically migrate your content if you have it still hosted on GitHub or GitLab (which it seems that you do! 😄)

Would you be interested in exploring this with me at all? Let me know, and I'd be happy to provide more information or even hop on a call to explain a bit more.

You can reach me here, or on email if that's easier—addison @ gitbook.com

Looking forward to hearing back from you!

Addison
Developer Relations @ GitBook

Automatic browser refresh

As far as I understand, the script tag pointing to the webpack-dev-server.js is the only thing needed to make the page reload on file change, and this is equal to using the --inline flag. (see http://webpack.github.io/docs/webpack-dev-server.html#automatic-refresh).

Adding the webpack/hot/dev-server to the entry point doesn‘t seem necessary, and this will throw "Uncaught Error: [HMR] Hot Module Replacement is disabled." if not launching the dev server with the --hot flag to enable Hot Module Replacement.

Optimizing rebundling

I am having issues with noParse and alias when following the "Optimizing rebundling" section. Following "Running minified file in development", when I try to require angular in my app, I just get an empty object returned.

WEBACK CONF

modules.noParse: [ '/Users/brandon/Desktop/webpack-babel/node_modules/angular/angular.min.js' ]
resolve.alias: { angular: '/Users/brandon/Desktop/webpack-babel/node_modules/angular/angular.min.js' }

APP

let angular = require('angular');
console.log('angular debug', angular, angular.module);

And in the logging statement, I get {}.

Any guidance or what might be wrong? Removing the noParse and alias will work fine, but I was hoping to use the minified versions for development.

Is this still in active development?

I have been working with webpack and angular on a a few large projects. I have just been making some demos, and would like to contribute more if this is still active?

Let me know?

error in Getting started chapter

Hi,

In Getting started you write the script "build": "webpack" in the package.json to use webpack with npm. But the webpack.config.js is located in the build dir. So how should this work? On my system it's only working if I move the webpack config in the project's root dir.

With "build": "webpack --config config/webpack.config.js" it works.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.