-
Notifications
You must be signed in to change notification settings - Fork 21
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
install fails with module missing errors #56
Comments
thanks Marcus, I'll add in prelim response from @kbeloborodko below, and lets continue this here; Thank you for providing the logs. They are very helpful. From what I can see you are missing bower dependencies as all of the errors that you get are based on the missing modules that are contained here https://github.com/PulseTile/PulseTile/blob/develop/bower.json. You mentioned that you executed bower install command successfully with a warning, but most likely corresponding bower components folder was not created for some reason. Could you please: 1. Clone a fresh copy of the repository |
Thanks @tony-shannon for posting @kbeloborodko's advice here I've reinstalled everything as per that advice and it's working now. A n00b error somewhere along the line on my part I reckon. Note that there were a number of deprecation warnings about (mainly) Angular packages that have now been renamed to the Angular.js namespace presumably to avoid clashing with Angular4 namespacing.
|
thanks Marcus
Kirill , do u want to update naming of packages accordingly?
thanks
T
…On 15 November 2017 at 17:46, Marcus Baw ***@***.***> wrote:
Thanks @tony-shannon <https://github.com/tony-shannon> for posting
@kbeloborodko <https://github.com/kbeloborodko>'s advice here
I've reinstalled everything as per that advice and it's working now. A
n00b error somewhere along the line on my part I reckon.
Note that there were a number of deprecation warnings about (mainly)
Angular packages that have now been renamed to the Angular.js namespace
presumably to avoid clashing with Angular4 namespacing.
npm WARN deprecated ***@***.***: 🙌 Thanks for using Babel: we recommend using babel-preset-env now: please read babeljs.io/env to update!
npm WARN deprecated ***@***.***: Use npmjs.com/husky instead, see ghooks-org/ghooks#166
npm WARN deprecated ***@***.***: This npm package 'angular-ui-router' has been renamed to ***@***.***/angularjs'. Please update your package.json. See https://ui-router.github.io/blog/uirouter-scoped-packages/
npm WARN deprecated ***@***.***: Package is deprecated, use https://github.com/deepsweet/istanbul-instrumenter-loader
npm WARN deprecated ***@***.***: this package has been reintegrated into npm and is now out of date with respect to npm
npm WARN deprecated ***@***.***: Use uuid module instead
npm WARN deprecated ***@***.***: Please update conventional-changelog to >1.0.0. If you are running the cli, use conventional-changelog-cli
> @***@***.*** install ***@***.***/core
> node ./migrate/migratewarn.js
> ***@***.*** install /home/marcus/code/ripple/PulseTile/node_modules/angular-ui-router
> node migrate/migratewarn.js
WARNING! this npm package "angular-ui-router" has been renamed to ***@***.***/angularjs". Please update your package.json
See https://ui-router.github.io/blog/uirouter-scoped-packages/ for details.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#56 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AA5X3BPRqq4Whsm_NRD72gFiOlvb77_Uks5s2yODgaJpZM4QfNFv>
.
|
@tony-shannon package names are constantly changing and some versions become deprecated. I think it is a good idea to revisit our package.json once in a certain period of time (two-weeks or a month for example). We will add this task to our backlog with @anna-otrokhova |
Good idea
thanks Kirill
T
…On 23 November 2017 at 09:54, kbeloborodko ***@***.***> wrote:
@tony-shannon <https://github.com/tony-shannon> package names are
constantly changing and some versions become deprecated. I think it is a
good idea to revisit our package.json once in a certain period of time
(two-weeks or a month for example). We will add this task to our backlog
with @anna-otrokhova <https://github.com/anna-otrokhova>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#56 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AA5X3FGCq6jRWxC1WGSG0sau3_PhSG0Yks5s5UC7gaJpZM4QfNFv>
.
|
|
I suppose it can be closed. As the issue was solved |
I'm sure this is just going to be something silly I'm doing wrong (or not doing) but I'm getting a few errors when I try to build and run PulseTile locally, following the instructions here: https://github.com/PulseTile/PulseTile
git clone
the repocd /path/to/repo
npm install
completes with a couple of npm WARN onlybower install
completes with a warning that we should start using Yarn :-) fair enoughnpm start
ornpm run build
both fail with errors:Not sure where these libraries are supposed to be coming from?
I would have imagined all js dependencies get installed by npm?
The text was updated successfully, but these errors were encountered: