Angular is not respecting browser field in package.json
Repro steps:
npm install @angular/cli
npx ng new my-app(press enter for defaults to prompts)cd my-app
npx ng build(notice that it works)npm install --save ethers- Add
import { BigNumber } from 'ethers/utils'tomy-app/src/app/app.component.ts
- Add
foo = new BigNumber(0)to theAppComponentclass inmy-app/src/app/app.component.ts
npx ng build(notice that it fails)
The problem here is that the ethers library has a package.json with:
{
"main": "./index.js",
"browser": "./dist/ethers.min.js",
}
According to the webpack documentation, webpack should be using ./dist/ethers.min.js. However, from the errors we can see that it is trying to use ./index.js, based on the fact that it is trying to read files that are part of the NodeJS build, rather than the browser build (which lives entirely in dist subdirectory).
Why isn't Angular respecting the browser field in package.json? What do I need to do in order to resolve this issue?
angular
asked Nov 18 '18 at 1:51
Micah ZoltuMicah Zoltu
2,88223055
add a comment |
Repro steps:
npm install @angular/cli
npx ng new my-app(press enter for defaults to prompts)cd my-app
npx ng build(notice that it works)npm install --save ethers- Add
import { BigNumber } from 'ethers/utils'tomy-app/src/app/app.component.ts
- Add
foo = new BigNumber(0)to theAppComponentclass inmy-app/src/app/app.component.ts
npx ng build(notice that it fails)
The problem here is that the ethers library has a package.json with:
{
"main": "./index.js",
"browser": "./dist/ethers.min.js",
}
According to the webpack documentation, webpack should be using ./dist/ethers.min.js. However, from the errors we can see that it is trying to use ./index.js, based on the fact that it is trying to read files that are part of the NodeJS build, rather than the browser build (which lives entirely in dist subdirectory).
Why isn't Angular respecting the browser field in package.json? What do I need to do in order to resolve this issue?
angular
asked Nov 18 '18 at 1:51
Micah ZoltuMicah Zoltu
2,88223055
add a comment |
Repro steps:
npm install @angular/cli
npx ng new my-app(press enter for defaults to prompts)cd my-app
npx ng build(notice that it works)npm install --save ethers- Add
import { BigNumber } from 'ethers/utils'tomy-app/src/app/app.component.ts
- Add
foo = new BigNumber(0)to theAppComponentclass inmy-app/src/app/app.component.ts
npx ng build(notice that it fails)
The problem here is that the ethers library has a package.json with:
{
"main": "./index.js",
"browser": "./dist/ethers.min.js",
}
According to the webpack documentation, webpack should be using ./dist/ethers.min.js. However, from the errors we can see that it is trying to use ./index.js, based on the fact that it is trying to read files that are part of the NodeJS build, rather than the browser build (which lives entirely in dist subdirectory).
Why isn't Angular respecting the browser field in package.json? What do I need to do in order to resolve this issue?
angular
asked Nov 18 '18 at 1:51
Micah ZoltuMicah Zoltu
2,88223055
Repro steps:
npm install @angular/cli
npx ng new my-app(press enter for defaults to prompts)cd my-app
npx ng build(notice that it works)npm install --save ethers- Add
import { BigNumber } from 'ethers/utils'tomy-app/src/app/app.component.ts
- Add
foo = new BigNumber(0)to theAppComponentclass inmy-app/src/app/app.component.ts
npx ng build(notice that it fails)
The problem here is that the ethers library has a package.json with:
{
"main": "./index.js",
"browser": "./dist/ethers.min.js",
}
According to the webpack documentation, webpack should be using ./dist/ethers.min.js. However, from the errors we can see that it is trying to use ./index.js, based on the fact that it is trying to read files that are part of the NodeJS build, rather than the browser build (which lives entirely in dist subdirectory).
Why isn't Angular respecting the browser field in package.json? What do I need to do in order to resolve this issue?
angular
angular
asked Nov 18 '18 at 1:51
Micah ZoltuMicah Zoltu
2,88223055
asked Nov 18 '18 at 1:51
Micah ZoltuMicah Zoltu
2,88223055
asked Nov 18 '18 at 1:51
Micah ZoltuMicah Zoltu
2,88223055
asked Nov 18 '18 at 1:51
Micah ZoltuMicah Zoltu
2,88223055
asked Nov 18 '18 at 1:51
Micah ZoltuMicah Zoltu
2,88223055
2,88223055
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
The issue was that I was doing imports in the form import { BigNumber } from 'ethers/utils'. This style of import bypasses the main or browser properties on the package.json, which means that I was pulling in the node version no matter what was in there.
The solution, never use import { ... } from '.../<something>' when you are importing from a mixed target dependency.
answered Nov 18 '18 at 2:20
Micah ZoltuMicah Zoltu
2,88223055
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53357222%2fangular-is-not-respecting-browser-field-in-package-json%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
The issue was that I was doing imports in the form import { BigNumber } from 'ethers/utils'. This style of import bypasses the main or browser properties on the package.json, which means that I was pulling in the node version no matter what was in there.
The solution, never use import { ... } from '.../<something>' when you are importing from a mixed target dependency.
answered Nov 18 '18 at 2:20
Micah ZoltuMicah Zoltu
2,88223055
add a comment |
The issue was that I was doing imports in the form import { BigNumber } from 'ethers/utils'. This style of import bypasses the main or browser properties on the package.json, which means that I was pulling in the node version no matter what was in there.
The solution, never use import { ... } from '.../<something>' when you are importing from a mixed target dependency.
answered Nov 18 '18 at 2:20
Micah ZoltuMicah Zoltu
2,88223055
add a comment |
The issue was that I was doing imports in the form import { BigNumber } from 'ethers/utils'. This style of import bypasses the main or browser properties on the package.json, which means that I was pulling in the node version no matter what was in there.
The solution, never use import { ... } from '.../<something>' when you are importing from a mixed target dependency.
answered Nov 18 '18 at 2:20
Micah ZoltuMicah Zoltu
2,88223055
The issue was that I was doing imports in the form import { BigNumber } from 'ethers/utils'. This style of import bypasses the main or browser properties on the package.json, which means that I was pulling in the node version no matter what was in there.
The solution, never use import { ... } from '.../<something>' when you are importing from a mixed target dependency.
answered Nov 18 '18 at 2:20
Micah ZoltuMicah Zoltu
2,88223055
answered Nov 18 '18 at 2:20
Micah ZoltuMicah Zoltu
2,88223055
answered Nov 18 '18 at 2:20
Micah ZoltuMicah Zoltu
2,88223055
answered Nov 18 '18 at 2:20
Micah ZoltuMicah Zoltu
2,88223055
2,88223055
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53357222%2fangular-is-not-respecting-browser-field-in-package-json%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
