[Loris-dev] installation difficulties
Shen Wang
wangshen.mcin at gmail.com
Mon Nov 29 08:59:18 EST 2021
Hi Rico,
Please update your node js version [NodeJS 16.10.0 (or higher)] , then
run "make" again.
I hope this will solve the problem.
Good luck
Best
Shen
On Mon, 29 Nov 2021 at 08:52, Rico_Díez.Olga <oricod at ext.cnio.es> wrote:
> Hello,
>
> I am having some difficulties installing Loris.
>
> The page that I have follow to install Loris is
> https://github.com/aces/Loris/blob/main/docs/wiki/00_SERVER_INSTALL_AND_CONFIGURATION/01_LORIS_Install/Ubuntu/README.md
>
> and also https://github.com/aces/Loris/wiki/Installing-Loris-in-Depth
>
> I have installed the versions on 0ubuntu0.20.04.1 for Linux on x86_64
> ((Ubuntu)):
> PHP 7.4.3
> mysql Ver 8.0.27
> Composer version 2.1.11
> Server version: Apache/2.4.41
> npm 8.1.4
> nodejs v10.19.0
>
> But an error keep showing when i do the "make" (Posted bellow):
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> *make tools/gen-version.sh npm install > loris at 1.0.0 postinstall > cd
> modules/electrophysiology_browser/jsx/react-series-data-viewer && npm
> install up to date in 2.438s up to date in 1m 314 packages are looking for
> funding run `npm fund` for details npm run compile > loris at 1.0.0 compile
> > webpack [webpack-cli] Invalid configuration object. Webpack has been
> initialized using a configuration object that does not match the API
> schema. - configuration[0].node has an unknown property 'fs'. These
> properties are valid: object { __dirname?, __filename?, global? } ->
> Options object for node compatibility features. - configuration[1].node
> has an unknown property 'fs'. These properties are valid: object {
> __dirname?, __filename?, global? } -> Options object for node
> compatibility features. - configuration[2].node has an unknown property
> 'fs'. These properties are valid: object { __dirname?, __filename?,
> global? } -> Options object for node compatibility features. -
> configuration[3].node has an unknown property 'fs'. These properties are
> valid: object { __dirname?, __filename?, global? } -> Options object
> for node compatibility features. - configuration[4].node has an unknown
> property 'fs'. These properties are valid: object { __dirname?,
> __filename?, global? } -> Options object for node compatibility
> features. - configuration[5].node has an unknown property 'fs'. These
> properties are valid: object { __dirname?, __filename?, global? } ->
> Options object for node compatibility features. - configuration[6].node
> has an unknown property 'fs'. These properties are valid: object {
> __dirname?, __filename?, global? } -> Options object for node
> compatibility features. - configuration[7].node has an unknown property
> 'fs'. These properties are valid: object { __dirname?, __filename?,
> global? } -> Options object for node compatibility features. -
> configuration[8].node has an unknown property 'fs'. These properties are
> valid: object { __dirname?, __filename?, global? } -> Options object
> for node compatibility features. - configuration[9].node has an unknown
> property 'fs'. These properties are valid: object { __dirname?,
> __filename?, global? } -> Options object for node compatibility
> features. - configuration[10].node has an unknown property 'fs'. These
> properties are valid: object { __dirname?, __filename?, global? } ->
> Options object for node compatibility features. - configuration[11].node
> has an unknown property 'fs'. These properties are valid: object {
> __dirname?, __filename?, global? } -> Options object for node
> compatibility features. - configuration[12].node has an unknown property
> 'fs'. These properties are valid: object { __dirname?, __filename?,
> global? } -> Options object for node compatibility features. -
> configuration[13].node has an unknown property 'fs'. These properties are
> valid: object { __dirname?, __filename?, global? } -> Options object
> for node compatibility features. - configuration[14].node has an unknown
> property 'fs'. These properties are valid: object { __dirname?,
> __filename?, global? } -> Options object for node compatibility
> features. - configuration[15].node has an unknown property 'fs'. These
> properties are valid: object { __dirname?, __filename?, global? } ->
> Options object for node compatibility features. - configuration[16].node
> has an unknown property 'fs'. These properties are valid: object {
> __dirname?, __filename?, global? } -> Options object for node
> compatibility features. - configuration[17].node has an unknown property
> 'fs'. These properties are valid: object { __dirname?, __filename?,
> global? } -> Options object for node compatibility features. -
> configuration[18].node has an unknown property 'fs'. These properties are
> valid: object { __dirname?, __filename?, global? } -> Options object
> for node compatibility features. - configuration[19].node has an unknown
> property 'fs'. These properties are valid: object { __dirname?,
> __filename?, global? } -> Options object for node compatibility
> features. - configuration[20].node has an unknown property 'fs'. These
> properties are valid: object { __dirname?, __filename?, global? } ->
> Options object for node compatibility features. - configuration[21].node
> has an unknown property 'fs'. These properties are valid: object {
> __dirname?, __filename?, global? } -> Options object for node
> compatibility features. - configuration[22].node has an unknown property
> 'fs'. These properties are valid: object { __dirname?, __filename?,
> global? } -> Options object for node compatibility features. -
> configuration[23].node has an unknown property 'fs'. These properties are
> valid: object { __dirname?, __filename?, global? } -> Options object
> for node compatibility features. - configuration[24].node has an unknown
> property 'fs'. These properties are valid: object { __dirname?,
> __filename?, global? } -> Options object for node compatibility
> features. - configuration[25].node has an unknown property 'fs'. These
> properties are valid: object { __dirname?, __filename?, global? } ->
> Options object for node compatibility features. - configuration[26].node
> has an unknown property 'fs'. These properties are valid: object {
> __dirname?, __filename?, global? } -> Options object for node
> compatibility features. - configuration[27].node has an unknown property
> 'fs'. These properties are valid: object { __dirname?, __filename?,
> global? } -> Options object for node compatibility features. -
> configuration[28].node has an unknown property 'fs'. These properties are
> valid: object { __dirname?, __filename?, global? } -> Options object
> for node compatibility features. - configuration[29].node has an unknown
> property 'fs'. These properties are valid: object { __dirname?,
> __filename?, global? } -> Options object for node compatibility
> features. - configuration[30].node has an unknown property 'fs'. These
> properties are valid: object { __dirname?, __filename?, global? } ->
> Options object for node compatibility features. - configuration[31].node
> has an unknown property 'fs'. These properties are valid: object {
> __dirname?, __filename?, global? } -> Options object for node
> compatibility features. - configuration[32].node has an unknown property
> 'fs'. These properties are valid: object { __dirname?, __filename?,
> global? } -> Options object for node compatibility features. -
> configuration[33].node has an unknown property 'fs'. These properties are
> valid: object { __dirname?, __filename?, global? } -> Options object
> for node compatibility features. - configuration[34].node has an unknown
> property 'fs'. These properties are valid: object { __dirname?,
> __filename?, global? } -> Options object for node compatibility
> features. - configuration[35].node has an unknown property 'fs'. These
> properties are valid: object { __dirname?, __filename?, global? } ->
> Options object for node compatibility features. - configuration[36].node
> has an unknown property 'fs'. These properties are valid: object {
> __dirname?, __filename?, global? } -> Options object for node
> compatibility features. - configuration[37].node has an unknown property
> 'fs'. These properties are valid: object { __dirname?, __filename?,
> global? } -> Options object for node compatibility features. -
> configuration[38].node has an unknown property 'fs'. These properties are
> valid: object { __dirname?, __filename?, global? } -> Options object
> for node compatibility features. - configuration[39].node has an unknown
> property 'fs'. These properties are valid: object { __dirname?,
> __filename?, global? } -> Options object for node compatibility
> features. make: *** [Makefile:15: javascript] Error 2*
>
> What is going on?
>
> Thanks in advance,
> Olga
>
>
>
>
> [image: Hazte Amigo del CNIO. Más investigación, menos cáncer]
> <https://www.cnio.es/es/colaborar/comocolaborar.asp>
>
> *Fb* Amigos del CNIO <https://www.facebook.com/AmigosdelCNIO/> | *Tw*
> @CNIOStopCancer <https://twitter.com/CNIOStopCancer> | *Youtube*
> canalcnio <https://www.youtube.com/canalcnio>
>
>
> **ADVERTENCIA LEGAL**: Este correo electrónico, y en su caso los ficheros
> adjuntos, pueden contener información protegida para el uso exclusivo de su
> destinatario. Se prohíbe la distribución, reproducción o cualquier otro
> tipo de transmisión por parte de otra persona que no sea el destinatario.
> Si usted recibe por error este correo, se ruega comunicarlo al remitente y
> borrar el mensaje recibido.
> De conformidad con lo dispuesto en el Reglamento (UE) 2016/679 relativo a
> la protección de los datos personales de las personas físicas, la
> información personal que nos pueda facilitar a través de este correo
> electrónico quedará registrada por la Fundación CNIO con la finalidad de
> tramitar el objeto del presente correo electrónico. El tratamiento de sus
> datos personales se encuentra legitimado por ser necesario para gestionar
> el objeto del presente mensaje. Estos datos personales no serán comunicados
> a ningún destinatario salvo a aquellos que usted nos autorice o así venga
> exigido por una ley. Ud. podrá ejercer los derechos de acceso,
> rectificación, supresión, limitación de tratamiento, portabilidad y
> oposición en la siguiente dirección: c/Melchor Fernandez Almagro 3, 28029
> (Madrid). Podrá ponerse en contacto con el Delegado de Protección de Datos
> en: delegado_lopd at cnio.es. Para el caso de que Ud. precise conocer
> información adicional sobre el tratamiento de sus datos personales, puede
> consultar dicha información adicional en el siguiente enlace dentro de
> nuestra página web: https://www.cnio.es/es/privacidad/index.asp
>
> **LEGAL NOTICE**: This email and any attached files may contain protected
> information for the sole use of its intended recipient or addressee. Anyone
> other than the intended recipient or addressee is strictly prohibited from
> distributing, reproducing or transmitting the email and its contents in any
> way. If you receive this email in error, please notify the sender and
> delete the message.
> Pursuant to the provisions of EU Regulation 2016/679 regarding the
> protection of personal data, any personal information you provide through
> this email will be registered by the CNIO Foundation in order to deal with
> content of this email. Your personal data must be processed in order to be
> able to deal with the content and purpose of this message. Your personal
> details will not be passed on to anyone else unless you authorise us to do
> so or we are required to do so by law. You may exercise your rights
> regarding access, rectification, suppression, limitation of processing,
> portability and opposition by writing to the following address: c/Melchor
> Fernandez Almagro 3, 28029 (Madrid). You may contact the Data Protection
> Delegate (Delegado de Protección de Datos) at: delegado_lopd at cnio.es. If
> you require further information about the processing of your personal data,
> go to the following link on our webpage:
> https://www.cnio.es/es/privacidad/index.asp
> _______________________________________________
> Loris-dev mailing list
> Loris-dev at bic.mni.mcgill.ca
> https://mailman.bic.mni.mcgill.ca/mailman/listinfo/loris-dev
>
--
Shen Wang
Loris <https://github.com/aces/Loris> Developer
Montreal Neurological Institute
McGill University
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.bic.mni.mcgill.ca/pipermail/loris-dev/attachments/20211129/8262746d/attachment-0001.html>
More information about the Loris-dev
mailing list