Closed trusktr closed 6 years ago
Not sure if this has any impact on the application, as it seems to still run fine even though that error is in the console. Maybe I'm not using any features related to that package.
Ah, I also see that the error relates to Akryum:vue
(cc @Akryum. Any ideas? Maybe I just need to update Akryum:vue-component (I'm on 0.13.0 and I see 0.13.1 is out. Will try it later... EDIT: same error with 0.13.1. Is vue-component dependending on an indirect depdency of meteor-node-stubs instead of the dependency itself?)
The problem stems from this line in akryum:vue-component
, which broken due to this (necessary) change in meteor-node-stubs
: https://github.com/meteor/node-stubs/commit/488059954d67e397432dea3b6dbe7696ee82939e.
The akryum:vue-component
package will need to be updated. If it's used in client code (as it appears to be), I'd expect this could be fixed by import
-ing from the http
module, which we map to the desired implementation on behalf of client code:
import Response from 'http/lib/response';
...though alternatively, it would have to be changed to use stream-http
instead of the unmaintained (And therefore no longer installed by meteor-node-stubs
) http-browserify
.
When upgrading from 0.3.2 to 0.3.3, an error begins to happen on the client side.
Check out the following repo at the following commit: https://github.com/trusktr/chat-widget/commit/09dff02f67cc1a5ba0ff12c3367b5aa4e688bbd4
If you
npm install && meteor
it will work just fine.Then, if you open
package.json
and change themeteor-node-stubs
version from^0.3.2
to^0.3.3
and runnpm install
(this updatespackage-lock.json
), then restart the meteor app, you'll get an error like this in browser console: