-
Notifications
You must be signed in to change notification settings - Fork 12k
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
3rd Party Library Installation with webpack #1696
Comments
@TheLarkInn can you have a look? |
I'm starting to get the feeling we will need to expose the node builtins. @hansl |
Hey guys! We're facing the same behavior, trying to use AutobahnJS:
Could you give a hint on how that can be sorted? |
update: the only way I've manage to sort it is to directly edit the Webpack common config file in Thanks. |
There is no 'proper' way at the moment, but this will be implemented one we have our add-on system implemented. |
coolio, looking forward to put my hands on it Many thanks! |
@TheLarkInn what would you recommend people to do until that is implemented then? Would you mind explaining the steps of installing a 3rd party app to make it clear for the rest of the people until we have a permanent fix for this? I taught a major reason behind switching to webpack was that it would fix this issue? |
@RicardoVaranda the readme has instructions on how to add 3rd party libs, this is IMHO a special case where the lib relies on node runtime built-ins. |
You are right after looking at the updated readme one I learnt about app [0].scripts which is now used and solved all my issues! |
Am I missing something? I followed the instructions in the readme.
|
@ecollis6 Looks good to me, are you having problems with that config? |
Same problem with both styles and scripts in "apps": [
{
"main": "src/main.ts",
"tsconfig": "src/tsconfig.json",
"mobile": false,
"styles": [
"src/styles.scss"
],
"scripts": [
"node_modules/hammerjs/hammer.min.js",
"node_modules/d3/d3.min.js"
]
}
], Update: My bad! Had webpack.8 in global and webpack.2 in local, plus all the deprecated configs of webpack.2. Changed it and it's working! |
Why minified version? |
@TheLarkInn habit. I know webpack will minify. Although it's not relevant if it's minified or not. |
Any updates on this guys? With beta.15 I still need to manually add |
I am also getting similar error while using |
@chiefmc I tried setting I'm not familiar with Maybe it solves your problem though, so I'll make a PR for it. |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Hi, I'm trying to install a 3rd party library, generated with browsify (https://github.com/bitpay/bitcore-wallet-client), works well with Angular 1 in production.
But now trying to install with webpack, and fail.
I'm doing this in a component, for example:
The problem is with request (request/request#1529) library used.
The log:
So, adding a webpack-config.js in https://github.com/bitpay/bitcore-wallet-client will solve the problem? Or we need to add this...
in angular-cli webpack config file? Like we done here (#1599) with
fs
?Thanks.
The text was updated successfully, but these errors were encountered: