share-code

I am attempting to export a simple object variable from a server side JS file to a client side JS file. In the server side file I am doing some web-scraping that ultimately results in a simple object variable. In the client side file I want to be able to access that variable.

I have found that I am indeed able to export a variable, but, if there is any commonJS syntax (correct me if I'm wrong) present in the server side file, then it will not work. The client side file will attempt to read the entire server side file including the commonJS syntax - which it can't.

The following code demonstrates my code and the issue:

Server side file:

• client and server both share a folder shared
• when we change shared in our development flow, we want the corresponding references to change in customer and server
• server works because somehow with npm it seems to work, shared and server use npm
• customer doesn't work and uses yarn
• mixed typescript and js project

I have some common code between two project solutions, and I would like to link a source file from one solution to another. Specifically, I would like to add/link a single .cs file from a different solution to my current one.

This seems to be a good answer. However, Visual Studio Code does not have the add as link or add existing item. It only have Add Folder to Workplace. Furthermore,dotnet add and dotnet sln add only takes .csproj file, which is the whole project.

So how do I achieve this?

I have a common library that I want to share between a few solutions, that stored in different github repositories. We put the shared library in separate GitHub repository and created nuget package, that can be installed in each required projects/solution. The disadvantage is that changing code in a library involves a few steps ( change code, push to library repository, creating nuget package, installing package) which is annoying.

I wanted to use git subtree to create sub directory with library project and use it as local project in my solution with easy code changing/testing/debugging. Developers of "Main" solutions will have a choice- include library as a binary nuget package or as a source project in subdirectory.

PROBLEM: When I tried git subtree, I found one issue: csproj files have relative references to packages folder, that are located on different levels, when included in standalone library solution and when included in a main solution. When in MyLib.sln the path is "..\Packages" , but in Main.sln the path should be "..\..\Packages" .
The structure of Main GitHub Repository ( and OtherUserOfMyLib GitHub Repository(is)) :

Numerous posts make it clear that using a shared Dropbox folder as a git remote can lead to problems.

However, opinions seem more mixed about placing a local repository (e.g. cloned from Github) into a private Dropbox folder.

My question is twofold:

1) Is it dangerous to place a local repository in a private Dropbox folder (that syncs across multiple computers, all owned by me)?

2) Is my remote repo (on GitHub) in danger if a collaborator chooses to sync their local repository to Dropbox (i.e. a collaborator clones the repository to Dropbox and regularly commits and pushes)?

I'm trying to use Visual Studio code to create a Azure Function micro-service (javascript and Functions v2) that I push to my VSTS account, that then triggers a CI-CD to Azure functions.

How do I configure the Azure Functions CI-CD process to bring across all of the files in my VSTS git repo?

Has anyone gotten this working? Is there a better way to connect the Azure Function to a CosmosDb while having shared javascript model files (I've seen numerous examples in C# on microsoft, but not for Javascript)?

Preferred dev env: VS Code -> VSTS Git CI-CD -> Azure Function -> Azure CosmosDb

What I'm trying to achieve:

• Step 1: I did a great tutorial that gets an Angular page linking to a Azure Http Trigger Function (https://dzone.com/articles/create-a-serverless-angular-app-with-azure-functio)
• Step 2: I like Visual Studio Code and want to be able to use it to develop a more sophistacated micro-service (https://www.michaelcrump.net/azure-tips-and-tricks50/)
• Step 3: I managed to do the advised "Upload" to Azure and the functions arived and worked ... nice one old-mate! (https://www.michaelcrump.net/azure-tips-and-tricks52/)
• Step 4: I pushed my 2 Functions (one from first tutorial and the other just the standard Hello-world created in VS Code) to VSTS, and created a Azure side CI-CD pull. This works, but VSTS has no Build or Deploy scripts I can see or edit. [https://docs.microsoft.com/en-us/azure/azure-functions/functions-continuous-deployment]
• Step 5: I want to create a RESTful Azure Function microservice to use mongoose and connect to Azure CosmosDb. This is the best I can find that suggests how using Azure CLI. (http://thecodebarbarian.com/getting-started-with-azure-functions-and-mongodb.html)
• Step 6: I want to have a shared model files as the microservice becomes more sophisticated. (How to share code in JavaScript Azure Functions?)

Problem ... The CI-CD I setup in Azure Function isn't bringing my shared sub-directory over and therefore the entire Function breaks. The CI-CD in VSTS doesn't include any details of the CI-CD Build and Release steps in the VSTS web UI (no processes are setup).

How do you create a shared subdirectory between functions?

I'm trying to do google authentication in my website, where the user gets authenticated on a page. After authentication, it generates a code which contains access_token and refresh_token, and I want to send it to my Node server.

I know Xhttp is a way but I want to avoid that.
So I tried using handle bars. But they only work for html right?

Is there anyway I could use something like helpers to send my code to the server?

I tried to get around some posts like:

• How can I share code between Node.js and the browser? (which is quite old, Node must've evolved till then right ?)

• Sending data from javascript/html page to Express NodeJS server (I didn't understand this one honestly)

I'm new to Node.js so any guesses or any reference to the docs?

I want to share common JS code between different JS projects in a very easy way. I thought about creating a Bower component (see: LINK) or a private NPM component (see: LINK).

However, I want it to be used in a very IDE friendly way. A such, that when we update the Common code (project) we don't need to first publish the changed Common code.

Let me explain what I mean by how we do this in Java with Eclipse (we use mostly IntelliJ with Python and React JS currently): In a Java project we include Common Java code through a maven dependency, and also open the Common Java code as a project in Eclipse. Eclipse is then smart enough to see that it will include a direct link to the Common code project, instead of including the Common code as jar such that you don't need to first deploy the Common code project to the private repo when making changes to it.

We aren't experts in JS code yet, so how can we realise this same kind of friendly IDE usage with JS ?