I'm trying to build a simple frontend example of machine learning using ml5.js, my problem is that one of the key feature I need has been merged to the master branch only five days ago and has not been added to the released min.js linked in the readme.md.
I was wondering if it was possible to build myself a minified version of the library using the code from the latest commit.
Thanks in advance
In fact I was just missing some instruction from the CONTRIBUTION.md
It was just a matter of cloning the repository and then run npm install & run
Related
we're working through a setup at my work and I want to see if anyone has any advice/best practices for what we're doing here.
We have code in a git repo for our ui library that produces an npm package (in an internal private registry). That package then gets pulled into the git repos for each of the main products. The question is about versioning the package.
Because we're going from a parallel dev process (git) to linear package versions, which then gets pulled back into another parallel dev process (product git repos), there's an opportunity for code from the library to be accidentally released to production:
Change A is made to the library, produces v1.0
Change B is made to the library, produces v1.1
The library version in a product is updated to v1.1 to access Change B
Product change, and v1.1, is released; Change A in v1.0 is accidentally included
Does anyone have any advice, best practices, or alternate workflows we could keep in mind? The main thing is, we want the UI library stored in one repo but able to be pulled into multiple other repos.
Thank you!
all! I currently met a difficulty with my project. I want to modify the code of a component from a UI library (like Semantic-UI, Material-UI). What I do now is just edited the code from the node_modules. But the reality is no matter how I change the code from node_modules, my project will not be affected. Why this will
Well that's because most modules have build process which you need to run before using them. Also editing a module directly is not a good idea because any change you do to them is guaranteed to be lost after next npm install.
As Vuetify is a MIT licensed, I suggest to fork its GitHub project and then publish it as your own npm package.
Does it is needed to install npm ethereumjs-tx while using a browser version of it which is directly downloaded from github.
If yes then how we can import the ethereumjs-tx module in our script file.
Because both are two different things as my knowledge.
ethereumjs-tx as a browser build can be found here
If it helps anyone in the future. EthereumJS community have created browser builds for most of their repositories here. Please use with caution as it has not been updated regularly. But they have put instructions on how to create a build for the latest versions over here
So can anyone help me get the AngularJS intellisense working in Visual Studio Code?
Is it possible to configure this globally or can it only per project? I'm preferably looking for a solution on how to do this globally, as in whenever I open VSCode AngularJS intellisense just works.
I'm currently using AngularJS 1.5.x. I do not know if it possible to configure according to the version of AngularJS being used. Additionally, I'm using VSCode 1.10.2 and VSCode - Insiders on Windows 10.
I've already searched in several places, but the solutions I've found did not work for me. Maybe it's because they are old.
There are many extensions available for intellisense in Angular (2+), but not for AngularJS. However, this article by Mike Barlow explains how to do it and it's fairly recent since you've asked your question (June 2016).
Here's the summary of what you need to do per the article:
Have the following tools installed: node.js 6.2+, npm 3.9+, and VSCode 1.2+.
Install the typings package globally: npm install -g typings. Make sure this is a 1.X version.
Install AngularJS types: typings install dt~angular --save --global
This should create a a folder typings\globals\angular\ with a file called "typings.json"
Create a file within this directory as a sibling to "typings.json" called "jsconfig.json". This file can remain empty unless you need to transpile code (ie, using typescript, coffeescript, etc.)
Restart VSCode
I am trying to upgrade a repo that currently uses a library that is in version 3. I want to be able to create a branch (BranchB) that is specific to updating this library to version 4. So I tried changing the package.json on BranchB to use v4 and did an npm install in order to get the correct version on this new branch.
I run the tests and they fail. Perfect.
Now when I switch back to master, I would prefer that the library version being used is set back to v3. Is there a Git workflow to make this possible? Or will I keep having to npm install every time I want the appropriate branch to have the correct corresponding library versions?
One possible strategy, albeit a bit clunky, is to clone the repo twice to different folders - one with the older library, one with the newer. Then just pretend that you've got split personality and edit the projects as two different programmers :)
As I said, it's clunky but it's better than constantly installing the libraries.