-
Notifications
You must be signed in to change notification settings - Fork 157
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
NPM update #161
NPM update #161
Conversation
…endency (not needed in readium-electron)
I am getting a build failure on Linux (fine on MacOS) ... investigating :( |
Linux failure (TypeScript compiler / WebPack loader): Works fine on MacOS, so I compared the contents of the |
Downgrading from NPM |
Just as I suspected, |
… ci instead of npm install ... let's see.
Travis CI now passes :) |
Note that |
…locator API. Backend database / store currently remains with only CSS selector support (string)
Note that the |
|
Also, should be a simple fix:
|
Thank you for the heads-up about "react-tap-event-plugin". As people have stated in the issue tracker ( zilverline/react-tap-event-plugin#121 ): "this plugin was never supported officially and relies on private APIs that can change in any patch", and "I think it's time to end this plugin" :) |
Regarding Note that I use the NCU utility to check for the latest available versions (minor and major updates). The goal is to explicitly include minor changes (to stay in sync with security updates, bug fixes, improvements, etc.), whilst filtering-out known breaking API updates. In the latter case, the So, thank you for the heads-up about |
@danielweck I am not really worried about the UI itself, I am trying to build the LCP stack, but so far I am not sure whether my |
@leomoty here is a copy-paste of the error you mentioned here #162 (comment) :
Are you sure you have a clean Git local copy of the branch? (please |
|
Trying to clone again on Windows
Will report back after |
Errors have changed:
I just omitted my absolute path, everything else is verbatim. |
Note that I've had build failures in the past with NodeJS version |
Note that the |
It is worth noting that TravisCI (Linux) successfully builds this PR branch See: |
I am currently running |
It doesn't seem to be first level packages tho:
|
Okay, I was able to successfully load it:
It compiled now. I have no clue what is the issue, but running |
Makes sense. Not. |
Also, I know for sure it is my issue now, I guess:
I think some config from |
Thank you for your debunking of this NPM issue. So it is now quite clear that GitHub dependencies ( as officially supported by NPM https://docs.npmjs.com/cli/install ) are problematic, requiring an extra |
@danielweck this is not the first time I have issues with npm, which is why I guess people suggests yarn? I can't say for sure, never used it myself. I'll try to go back to make the |
@leomoty can you please log an issue at https://github.com/edrlab/r2-lcp-js/ |
Done, readium/r2-lcp-js#2 |
I filed a separate issue regarding Material-UI: |
…te minor versions here in readium-desktop
…eaks TypeScript check in typings!)
package.json
script "package:pack-only" forelectron-builder
(a separate branch will be created later, for the customized ASAR build process)Please merge this as soon as possible to avoid future branch conflicts :)
(if you approve, of course)