Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Eclipse Scout » Eclipse Scout 11 : NPM download root(NPM download root for the web app user interface)
Eclipse Scout 11 : NPM download root [message #1849262] Mon, 10 January 2022 14:23 Go to next message
Mark Ashworth is currently offline Mark AshworthFriend
Messages: 40
Registered: January 2012
Member
Good day,

I hope you had a great festive season.

I encountered an issue when upgrading an Eclipse Scout 10.0.45 application to 11.0.42, where the UI application build failed because of the certificate error when using https://registry.npmjs.org/ for downloading NPM dependencies.

Previously this was overwritten in the NPM Config on the local Node install but it seems that this no longer works.

I was wondering whether the frontend-maven-plug configuration in org.eclipse.scout:maven_rt_plugin_config-master would allow for the property npmDownloadRoot to be overwritten so that we could either proxy the NPM repo locally using Nexus or to use the http://registry.npmjs.org

https://github.com/eirslett/frontend-maven-plugin#installing-node-and-npm

Kind regards,
Mark Ashworth
Re: Eclipse Scout 11 : NPM download root [message #1849314 is a reply to message #1849262] Wed, 12 January 2022 14:18 Go to previous message
Matthias Villiger is currently offline Matthias VilligerFriend
Messages: 229
Registered: September 2011
Senior Member
Hi Mark

Thank you, yes, I hope you too! :)

You are right, in Scout 11 the Maven build by default downloads a fresh Node and only uses this for building. So maybe that's why your configs are no longer active? Where exactly did you apply this configuration? In an .npmrc file in your user home or where exactly?

I don't understand why you get certificate errors for this URL. As far as I can see the certificate seems to be valid?

However, I have never used the npmDownloadRoot property but I assume it is only used while downloading the package. When using the package afterwards the property might no longer have an effect. But you can give it a try.

One other idea is to use the Maven property "master_node_dir". It allows you to specify a custom location for the Node installation to use. Maybe you can try to point this property to your local instance? You can configure it directly within your pom.xml or pass it as system property when executing Maven (e.g.: mvn clean install -Dmaster_node_dir=...).

Hope this helps
Mat
Previous Topic:unable to create signature
Next Topic:js not found when dev mode is turned off
Goto Forum:
  


Current Time: Thu Feb 22 20:14:45 GMT 2024

Powered by FUDForum. Page generated in 0.02364 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top