node-example | An example using create-react-app | Frontend Framework library

When you initiate the client you can either set strictSSL to false ( you did ) or pass in the new valid certificates.

Set strictSSL to false ( which you already did ) and then update cert files (you should be able to export them here - https://baltimore-cybertrust-root.chain-demos.digicert.com/)

This link http://registry.npmjs.org/npm could be block by IT admin in your organization. ( Please Verify )

In addition,You can refer to this stack overflow case as reference for the fix with secure manner and some various alternatives which might assist you for getting direction for the solution.

I'm going to guess from the title you're seeing a message like this in your CloudBuild logs:

It works!

PF the complete code on the github!

https://github.com/nandy2013/uploadFileOnFTP-express-fileupload

I received an answer from @dna2github, the creator of NodeBase (thanks a lot!) that I'll include here (with permission):

Hi,

Thx for your question. I will do a brief answer in my view.

pros:

• integrated with Java world; can get full control of code.

cons:

• a little hard to integrate with 3rd packages (need time to learn how).
• need to learn about NodeJS and V8 things and also J2V8 docs (it consume long time).

pros:

• focus on js dev and no need to consider android side.
• less learning time; similar to Cordova phonegap ....

cons:

• js app => apk is a black box.

pros:

• flexible

cons:

• no gui

Not familar with LiquidCore; build micro service especially from url, I think, is to resolve no direct available storage on iOS. react-native-node the Android part is based on NodeBase method and use the prebuilt binary.

For NodeBase:

pros:

• similar to 3; difference is that it has its own gui to start/stop app.
• it can be a template for everything; for example, if would like to run django, you just need to replace node to python; rails, ruby...

cons:

• native process access problem; the process cannot inherit access from Android app.
• happy toy happy open source not like a commercial app; need more design if want to distribute to customers

At first, I run node in terminal; I find only dev can easily to use it to start js app. My friends and families also wanna some tools for example make water mark on picture in batch. NodeBase is created for them to easy to start/stop app. Then they just need to open browser to use it. My another idea to create NodeBase is that we can build sharable applications that can be shared in the same Wi-Fi. When host starts an app, it can be visited by near people. Then they can work and play together. For example, we play werewolf and when there is no judge, we will start the werewolf app to have a judge for the first round. We can also share files between devices via download/upload.

For me, I can build what I want flexibly for example, I would like to make my Android as a machine learning runner; it can help me run machine learning programs at anytime (with node and python, thus in my another repo: dna2oslab is focus on building binaries) to make use of phone running time.

For you, if wanna port your app in a short time, I recommend 2; if you have time and other resources, 1 is better. 3 if you just make a toy/demo. 4 other is always possible and just do your imagination to create works.

Best wishes, Seven

No longer required as I found ImageCharts to be better suited to my needs.

The main problem is in line #5 and it's always a good idea to add the callback function for logging errors and successful requests.

Do I need both a client and a server?

Not necessarily. As the language support docs you linked show, there's usually two options: a "direct implementation" and one using the Language Server Protocol. For the former, you don't need a client / server architecture. Language Servers have the advantage of being editor-agnostic, you can theoretically use them in any editor that implements the protocol. A direct implementation is limited to usage in VSCode.

All I really want to do in my language is detect lines that start with @ and show them in the Go to Symbol pane.

Here's the extension.ts for a very simple example of a "direct implementation" for this:

You should only need to publish the extension itself (the client) and not the server.

The LSP example is a little weird because it shows the client and server folders side by side, whereas the server is actually a dependency of the client. You can either pull in the server as a node module or copy the server JS into the client like the example does. Then just run vsce publish in the client to push everything up to the marketplace

Can you please try the following?

1. Increase the tests timeout (currently at 2s)
2. set logLevel: 'DEBUG' in any pact({...}) declarations
3. Re-run the tests

And provide us a gist of the output.

It seems the Ruby mock server is not starting or is taking longer than 2 seconds, and the node process is timing out waiting for it to come up.

If that doesn't work, please try manually starting the mock service ./node_modules/bin/pact-mock-service --port 1234 and when it comes up, run the command netstat -an | grep LISTEN | grep 1234 so that we can see what network it is binding to.