In my angular-meteor project, I opted for using meteor's bootstrap package nemo64:bootstrap, for it's easy customization of the original bootstrap settings. However, when installing another meteor package for easy html text editor, the fraywing:text-angular..
When installed, the text-angular package installs twbs:bootstrap, which is another package to handle bootstrap, and this breaks most of my bootstrap javascript functions, because of the double call all of them recieve (one from the nemo64 and another form the twbs)..
I figured I could just uninstall the twbs:bootstrap package via meteor remove twbs:bootstrap but the command fails due to the package haven't been installed, because it comes bundled with the fraywing:text-angular package.
Is there any way I can remove that dependecy from text-angular, as I'm using nemo64's bootstrap package.
Thanks in advance.
This is the package list from meteor:
accounts-password 1.1.4 Password support for accounts
angular 1.3.5* Everything you need to use AngularJS in your Meteor app
angular:angular-sanitize 1.5.0 AngularJS (official) release. For full solution: http://angular-meteor.com/
angularui:angular-ui-router 0.2.15 angular-ui-router (official): Flexible routing with nested views in AngularJS
check 1.1.0 Check whether a value matches a pattern
email 1.0.8 Send email messages
es5-shim 4.1.14 Shims and polyfills to improve ECMAScript 5 support
fortawesome:fontawesome 4.5.0 Font Awesome (official): 500+ scalable vector icons, customizable via CSS, Retina friendly
fraywing:text-angular 1.3.11 A radically powerful Text-Editor/Wysiwyg editor for Angular.js!
jquery 1.11.4 Manipulate the DOM using CSS selectors
less 2.5.1 Leaner CSS language
meteor-base 1.0.1 Packages that every Meteor app needs
mobile-experience 1.0.1 Packages for a great mobile user experience
mongo 1.1.3 Adaptor for using MongoDB and Minimongo over DDP
mquandalle:bower 1.5.2_1 Use Bower packages in your Meteor app
natestrauser:animate-css 3.4.0 Animate.css packaged for meteor
nemo64:bootstrap 3.3.5_2 Highly configurable bootstrap integration.
session 1.1.1 Session variable
standard-minifiers 1.0.2 Standard minifiers used with Meteor apps by default.
timmyg:wow 1.0.1 WOW css animations
tmeasday:publish-counts 0.7.3 Publish the count of a cursor, in real time
tracker 1.0.9 Dependency tracker to allow reactive callbacks
urigo:angular-blaze-template 0.3.0 Include Blaze templates in your angular-meteor application.
You can copy the package locally and modify it: create a packages folder in root folder, clone the fraywing package into it from github then modify its dependencies in package.js to use the nemo package instead of twbs.
Meteor will automatically use your local packages over the one from the repository, the list command should show a little star next to the fraywing package to indicate it has picked up the local one. This would however mean the package would not update to the latest version with meteor update...
Related
I have a nodejs project using yarn as the package manager. The project includes a library (Library A), which has a dependency on Library B. Library B has a dependency on a Ruby Gem.
I am trying to figure out how to update the version of the Ruby Gem.
I tried updating Library B to its latest versions in the package.json file using a resolution tag, but I still can’t get the version of the Ruby Gem I need. Is there a way to update Ruby gems that are nested dependencies? Maybe something equivalent to the “resolutions” tag?
Thanks!
Why do I have to install Node.js to work with Polymer? Just because of npm? Are there any other uses for Node.js in a typical Polymer project? Or is npm just used to install Bower, and Bower to install project dependencies?
Node.js is just use to create project files. create a polymer project you have to use the console polymer CLI.
once files are generated you don't need the CLI until new project or to modify the current one.
You don't need Node.js. You can download all the components you want (plus all their dependencies and polyfills) from Github yourself, and organize them in your project directory. You also don't need any project files if you're going that route.
If you want, however, to conveniently install the components and all their dependencies, you can use bower, or the more recent yarn, which use Node.js. Also, if you want to host your project on Github or similar, it's useful to just commit bower.json which contains a list of all the dependencies (and can then conveniently be installed after cloning the repo), instead of forking all of Polymer's code into your project repo.
Having this said, if all you need is Polymer itself without any of the web components Polymer provides, it's probably even easier to just download Polymer and the required polyfills yourself.
There are more uses for Node.js. You may want to use some packages in your Polymer project, such as Redux, which you can also just download yourself, or install using NPM/Node.
I do not have Node.js installed on my machine.
I have been given the source code of an application that is coded in Node.js, Express and AngularJS.
To determine the Angular.js version like any other client side javascript library I can just open the filename and get the version.
In the root folder of my application there is a node_modules folder but there is nowhere I can see what version of Node.js it is for. It does have a debug subdirectory that contains Node.js but opening the file doesn't show me the version number.
When I go to the Node.js website it gives me two version options: 4.5 or 6.5. Which one should I use if I don't even know the version the source code is written in?
Since node.js is not bundled with the source code you have to find out yourself. Is there a package.json in the application's root directory? The desired node.js version might be declared at "engines". Beside that the dependencies of your application might have some requirements. So installing node.js 4.5 LTS and running npm install might give some insight.
Are tests present? If there's a reasonable code coverage, running them could give you some safety in guessing if every feature will work with your installed version of node.js.
Usually the dependencies listed in your package.json will dictate the node version you have to use. So if npm install works you're off to a good start. An exception may be if the original author used ES6 features, which means you have to run a quite recent version.
I am trying to figure out an effective way to bundle and distribute various dependencies (node modules and/or "client"-side scripts and framework like Angular) with my Electron App.
Although the basic approach of npm install module-name --save works well for development, it is not so good in the end when it comes to minimizing the size of your app and using minified resources at runtime. For instance, virtually all npm packages (including node modules) come with a lot of "extra baggage" like readmes, various versions of components (minified, not minified, ES2015, no-ES2015, etc). While these are great for development, all these files have absolutely no need to be included in the version you will be distributing.
Currently there seem to be 2 ways to sort of address the problem:
Electron Builder recommends using 2-file package.json system.
Any dependency that is used during development only should be npm-installed using --save-dev and then prunning should be used when building the app for distribution.
In that regard I have several questions:
I am not quite sure why there is a need for 2-file package.json system if one can install dev-only modules/ dependencies with --save-dev and then use pruning during the actual app build/compilation?
Regardless of which method above is used, you still end up with full npm packages in your app, inclduying all the miscellaneous/duplicated files that are not used by your app. So how does one "prune" so to speak the npm packages themselves so that only the actual files that are being used at run-time (like minified scripts) get included?
Will using Bower for "client-side" packages (like AngularJS 2, Bootstrap, jQuery, etc.) and using npm for node modules (like fs-extra) be a better option in as far as separation of concerns and ease of bundling later?
Could WebPack be used to produce only the needed files, at least for the "cient-side", so that only real node modules will be included with the app, while the rest of it will be in the form of web-pack compiled set of files?
Any practical tips on how this bundling of dependencies and distribution should be accredited out in practice? Gulp-scripts? Web-pack scripts? Project structure?
Thank you.
I am still in the learning curve of adopting the best practices in code deployment. But here is my starting list of what is recommended.
Yes, npm install --save-dev is the first easiest thing to isolate dev and build specific packages. This includes gulp/grunt/webpack and its loaders or additional packages. These are used only for building and never in the code that actually is run. All packages used by the app should be installed with npm install --save so that it is project level available. So, in production, you would no npm install --production in machines which will not install dev packages at all. See What's the difference between dependencies, devDependencies and peerDependencies in npm package.json file? for more info.
While the original recommendation was to use bower for client side and npm for server side, both can be installed using npm too. After all, both does the same job of managing the packages and dependencies. However, if web pack is used, it is recommended that npm is used for client side dependencies also.
package.json should be thought of managing the dependent packages only and not for building. For building and picking only the required files, you need task runners like gulp/grunt or bundlers like web pack.
While gulp/grunt is very popular for build automation which includes bundling all dependent javascript in file and minifying them in to one file, webpack/browserify is a better option as it supports module import. Module import is intuitive way of require one module in another in node js type of coding
var util = require('./myapp/lib/utils.js') This is powerful way of mentioning the required dependencies in the code. The web pack builder runs like gulp as build process. But instead of looking through html file for all js files, looks at starting js file and and determines all dependent code mentioned by the require statements recursively and packages accordingly. It also minifies the code. It also loads css and image files in one bundle to reduce server trips. If needed, some modules can be configured to be loaded at runtime dynamically further reducing page load. NPM vs. Bower vs. Browserify vs. Gulp vs. Grunt vs. Webpack discusses this at length.
Webpack can be used to bundle client side app optimally while server side need not be bundled or minified as there is no download.
In web pack, though you can mention dependent modules with lib file path, the recommendation is to npm install all dependencies and mention the module name. For example if you have installed jquery, instead of giving path like /libs/jquery.min.js, you can mention as 'jquery'. Webpack will automatically pull the jquery lib and dependencies and minimise it. If they are common modules, it will be chunked too. So, it is better to npm install dependent packages instead of bower install.
ES2015 provides lot of benefits during coding time including type checking and modules. However all browsers do not yet support the spec natively. So you need to transpile the code to older version that browsers understand. This is done by transpilers like Babel that can be run with gulp. Webpack has in-built babel loader so web pack understands ES2015. It is recommended to use ES2015 module system as it will soon become the defacto way of coding and since there is transpiler, there is no worry of this not being supported in IE8/9.
For project structure you could have
server
client
src containing js files
dist containing html and build files generated
webpack.dev.config.js and webpack.prod.config.js can be at root level.
I have found that this area is an ocean and different schools of best practices.This is probably one set of best practices. Feel free to choose the set that works for your scenario. Look forward for more comments to add to this set.
I started a tutorial on Angular 2.0, the first step in setting up the workspace is installing Node.js and NPM.
Why do we have install Node.js for Angular 2.0?
I don't remember doing this for angular 1.X.
Technically, Node.js and NPM are not needed to do Angular2 work. It does ease things though. Here's the main reasons I speculate are behind this choice:
CLI: Since a while now the de facto way to build and develop new Angular apps is to use the CLI tooling which relies on Node and NPM as well.
TypeScript: Examples are .ts, and you need to run a compiler step to get them into .js, which can be done on-the-fly easily with Node.js and NPM (plus it's a way of easily getting typing files);
Web Server: Serving your Angular SPA from a "real" albeit light web server prevents probably some nasty issues that come with checking your site using file:// links.
The Quickstart guide itself actually continues to mention some more concrete reasons as well:
Here's what these scripts do:
npm start - runs the compiler and a server at the same time, both in "watch mode"
npm run tsc - runs the TypeScript compiler once
npm run tsc:w - runs the TypeScript compiler in watch mode; the process keeps running, awaiting changes to TypeScript files and re-compiling when it sees them
npm run lite - runs the lite-server, a light-weight, static file server with excellent support for Angular apps that use routing
npm run typings - runs the typings tool separately
npm run postinstall - called by npm automatically after it successfully completes package installation. This script installs the TypeScript definition files defined in typings.json
You can also have a look at the Quickstart source and further dive into where NPM is needed.
Footnote: there's a similar question about needing Node.js for AngularJS (1.x).
Because Anglar2 is based on Typescript, Web Components and ES6 which need compilation for performance and broader browser support. Typescript is compiled to ES5 JavaScript and the other features require shims for backwards compatibility.
Since Typescript is a superset of JavaScript, and it's compiled to JavaScript anyway, you can write your code in plain JavaScript but it's not recommended.
For a more detailed explanation check out these videos on YouTube
Why Typescript
Instalation steps
NodeJS gives you the tool npm that allows you to download libraries and packages you would use in Angular 2. From the shell you can go to your folder and type npm install to install dependencies you need to have installed to get your angular project going. It will make it easier for you! If you want a complete starter kit go to https://github.com/buckyroberts, you can fork or download the zip with all the starter files to get you going :)
You do not need to use Node anywhere in production to use any front-end JavaScript framework, whether it is jQuery, AngularJS, ReactJS, Angular2, etc.
Angular2 can be used in isolation but to get and feel better development environment, angular2 should be used with nodejs and npm. Some of the nodejs modules helps you in web development.