{"action":"created","issue":{"url":"https://api.github.com/repos/GoogleChrome/workbox/issues/759","repository_url":"https://api.github.com/repos/GoogleChrome/workbox","labels_url":"https://api.github.com/repos/GoogleChrome/workbox/issues/759/labels{/name}","comments_url":"https://api.github.com/repos/GoogleChrome/workbox/issues/759/comments","events_url":"https://api.github.com/repos/GoogleChrome/workbox/issues/759/events","html_url":"https://github.com/GoogleChrome/workbox/issues/759","id":251713167,"number":759,"title":"workbox-build API Changes","user":{"login":"gauntface","id":139760,"avatar_url":"https://avatars0.githubusercontent.com/u/139760?v=4","gravatar_id":"","url":"https://api.github.com/users/gauntface","html_url":"https://github.com/gauntface","followers_url":"https://api.github.com/users/gauntface/followers","following_url":"https://api.github.com/users/gauntface/following{/other_user}","gists_url":"https://api.github.com/users/gauntface/gists{/gist_id}","starred_url":"https://api.github.com/users/gauntface/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/gauntface/subscriptions","organizations_url":"https://api.github.com/users/gauntface/orgs","repos_url":"https://api.github.com/users/gauntface/repos","events_url":"https://api.github.com/users/gauntface/events{/privacy}","received_events_url":"https://api.github.com/users/gauntface/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":1,"created_at":"2017-08-21T16:39:13Z","updated_at":"2017-09-06T18:25:52Z","closed_at":null,"author_association":"CONTRIBUTOR","body":"cc @jeffposnick @goldhand \r\n\r\nDuring the last meeting, the idea of changing of the `workbox-build` API came up. I believe this is around some of the API's being confusing to developer, i.e. when and how to use one or the other and then there is the topic of sharing some of the logic in `workbox-build` that isn't currently available (this might be making some of the API's public or just ensuring the internal logic can be shared with the webpack plugin).\r\n\r\nThings that have been mentioned a few time or were discussed during our meeting:\r\n1. One change that has been requested a few times is adding the ability to define a regex for the `injectManifest()` point.\r\n1. Webpack can generate it's own manifest\r\n    1. Will this help us to work with webpack server?\r\n    1. Will we be able to have the same filtering of files of certain size? glob pattern etc?\r\n1. The runtime caching could be extracted to a seperate internal file that webpack could use\r\n\r\n@jeffposnick did you have any additional ideas?\r\n\r\n"},"comment":{"url":"https://api.github.com/repos/GoogleChrome/workbox/issues/comments/327572325","html_url":"https://github.com/GoogleChrome/workbox/issues/759#issuecomment-327572325","issue_url":"https://api.github.com/repos/GoogleChrome/workbox/issues/759","id":327572325,"user":{"login":"goldhand","id":1919664,"avatar_url":"https://avatars2.githubusercontent.com/u/1919664?v=4","gravatar_id":"","url":"https://api.github.com/users/goldhand","html_url":"https://github.com/goldhand","followers_url":"https://api.github.com/users/goldhand/followers","following_url":"https://api.github.com/users/goldhand/following{/other_user}","gists_url":"https://api.github.com/users/goldhand/gists{/gist_id}","starred_url":"https://api.github.com/users/goldhand/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/goldhand/subscriptions","organizations_url":"https://api.github.com/users/goldhand/orgs","repos_url":"https://api.github.com/users/goldhand/repos","events_url":"https://api.github.com/users/goldhand/events{/privacy}","received_events_url":"https://api.github.com/users/goldhand/received_events","type":"User","site_admin":false},"created_at":"2017-09-06T18:25:52Z","updated_at":"2017-09-06T18:25:52Z","author_association":"COLLABORATOR","body":"> Webpack can generate it's own manifest\r\n\r\nI've found that webpack can generate and manage revisions for files. Chunks that come from webpack can be managed with `chunkhash` which only changes when the chunk does. Other assets (from webpack loaders and plugins) will have to be managed using the compilation hash.\r\n\r\n> Will this help us to work with webpack server?\r\n\r\nI am able to generate a service worker as a webpack asset so I think this will work with webpack-dev-server. Will test and update you.\r\n\r\n> Will we be able to have the same filtering of files of certain size? glob pattern etc?\r\n\r\nThe same filtering that webpack offers in it's loaders? Or is this from the workbox api?\r\n"}}
{"actor":{"display_login":"goldhand"}}