Skip to content
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

App "chromeapp" field to `package.json` #1691

Merged
merged 1 commit into from Aug 8, 2019
Merged

App "chromeapp" field to `package.json` #1691

merged 1 commit into from Aug 8, 2019
Commits on Aug 8, 2019
  1. App "chromeapp" field to `package.json`

    feross committed Aug 8, 2019
    I'm attempting to make a defacto standard for specifying Chrome App dependency substitutions using the `"chromeapp"` field in `package.json`.
    
    The `"chromeapp"` field is just like the [`"browser"` field in `package.json`](https://github.com/defunctzombie/package-browser-field-spec) except it's intended for Chrome Apps instead of a generic browser environment. Bundler tools like `browserify` or `webpack` can be configured to look for the `"chromeapp"` field instead of the `"browser"` field when doing a build for a Chrome App.
    
    In this specific package, since Chrome Apps can use raw sockets we want to replace e.g. `require('net')` with `require('chrome-net')`.
You can’t perform that action at this time.