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

Conversation

feross
Copy link
Member

@feross feross commented Aug 8, 2019

For: brave/brave-browser#5587

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 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').

I'm also sending PRs to all dependent projects that need substitutions to work in Chrome Apps.

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')`.
@feross
Copy link
Member Author

feross commented Aug 8, 2019

This will be part of 0.108.0

@feross feross mentioned this pull request Aug 9, 2019
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 30, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant