I just started the Discover Meteor Tutorial, and when I attempt to:
mrt add bootstrap
I get the following error:
usr/local/lib/node_modules/meteorite/lib/project.js:225
throw("Package named " + pkgName + " doesn't exist in your meteor in
^
Package named bootstrap doesn't exist in your meteor installation, smart.json, or on
atmosphere
Any thoughts? Thank you.
update 3/2/14:
It looks like the book now supports the official bootstrap package which you can get via:
$ meteor add twbs:bootstrap
old answer:
It looks like they have not updated the book for the new packaging system. You have some choices when it comes to which bootstrap version to use. I'm not sure which one the book expects, but you could try the default that comes with meteor:
$ meteor add bootstrap
Note we are replacing mrt with meteor.
If you want bootstrap 3, then you could try:
$ meteor add mizzao:bootstrap-3
mrt add bootstrap-3
is worked for me. Hope this help!
I had the same problem, but luckily, found a solution quite easily. It appears that the Meteorite package manager operates on packages that have already been added to your local project with meteor add <packageName> and allows you to manage them more conveniently with the smart.json and smart.lock files. Consequently, the steps you should take are the following:
Install bootstrap with meteor add bootstrap in your project (this operation does not write to smart.json);
Issue the command mrt add bootstrap (this command will record your bootstrap package in smart.json and smart.lock for easier package management with Meteorite).
Related
Long story short, I am currently creating an npm package for React Native that is dependent on other packages that are native and require linking, pod install, etc.
I am currently using peerDependencies to make it work but I would like to include everything in the package for people to enjoy an easy installation process instead of manually installing 3-6 dependencies themselves.
I am not sure where to start about that or if it's even possible, any thoughts are appreciated.
I think the first think you should check is this library. It's actually recommended by the official React Native documentation.
You can create basic bootstrap for your npm package with this command (check the link above to RN docs for more information):
npx create-react-native-library react-native-awesome-module
if you wanna use a native package then you will need for
IOS
you will need to add s.dependency in react-native-pkgname.podspec REF
Android
you will need to add implementation in android/build.gradle file REF
To make new package, you can use this CLI
https://github.com/callstack/react-native-builder-bob
npx create-react-native-library react-native-awesome-module
I want to add https://www.npmjs.com/package/react-dropzone to a React project written in TypeScript. And I am using the Yarn package manager.
So I hit the command yarn add #types/react-dropzone, which actually installs another deprecated package https://www.npmjs.com/package/#types/react-dropzone.
Currently in my package.json ->
"#types/react-dropzone": "^5.1.0"
I found something is wrong when I saw it working in Firefox but not in Chrome.
How can I install the actual package(https://www.npmjs.com/package/react-dropzone)?
As npm site says, you dont need #types/react-dropzone because the original package now contains everything needed.
I am using several open source js libraries in my project. I recently moved to use bower for all the front-end dependencies. I liked how I can just provide a github url instead of a proper package name.
I have customized few libraries. So to manage them using bower, I created a single private repository called myLibs in an organization account on Github.
I am creating branches for each customized library. For example, customized angular-bootstrap library will be in angular-bootstrap branch and customized angular-material library will be in angular-material branch.
Now I am creating tags for each release in each library. The naming convention that I am using is branch-name/x.y.z For example, I have angular-bootstrap/1.0.0 and angular-material/1.1.1 tags.
This was good till I had to install these libraries using bower. To install the custom libraries I called the following command (It's a dummy url, don't try it)
bower install --save-exact library-patch=https://github.com/test_org/myLibs.git#branch-name/1.0.0
The library gets installed and I can see it in bower_components too, but in my bower.json the dependency entry turns up like this -
"library-patch":"https://github.com/test_org/myLibs.git#undefined"
This is not what I wanted. I wanted to have the proper tag name to be saved. I don't want to manually make changes in the bower.json file every time I want to add a custom library.
My first thought was that the naming convention of the tags will be a problem. So I changed it to branch-name-x.y.z from branch-name/x.y.z which allowed me to have the exact version in the bower.json to install it properly, but when trying to install the libraries using the terminal, instead of using bower.json, I am getting the#undefined` tag in the end of the dependencies.
Here's the log I am getting while installing the library from terminal.
bower install --save-exact library-patch=https://github.com/test_org/myLibs.git#branch-name-1.0.0
bower not-cached https://github.com/test_org/myLibs.git#branch-name-1.0.0
bower resolve https://github.com/test_org/myLibs.git#branch-name-1.0.0
bower download https://github.com/test_org/myLibs/archive/branch-name-1.0.0.tar.gz
bower retry Download of https://github.com/test_org/myLibs/archive/branch-name-1.0.0.tar.gz failed with EHTTP, trying with git..
bower checkout library-patch#branch-name-1.0.0
bower resolved https://github.com/test_org/myLibs.git#branch-name-1.0.0
bower install library-patch#branch-name-1.0.0
library-patch#branch-name-1.0.0 bower_components/library-patch
└── angular#1.4.8
Why am I getting undefined in the release/tag name? Am I making any mistake while naming the tags? Is there any way I can install those custom libs from terminal and save the exact tag in bower.json?
The solution for the problem was to use --save instead of --save-exact. I have no explanation for the same right now, but I'll update the answer as soon as I can.
As far as I can tell, it's because the package was getting installed from github directly, instead of from bower registry.
I'm attempting to update my Phenomic install to webpack 2 beta 13 (I've heard people suggest the beta is pretty stable now).
I get the follow error when trying to build version using the DedupePlugin, but it seems to work if I remove it. The error is:
phenomic:builder ChunkRenderError: No template for dependency: TemplateArgumentDependency
at Compilation.createChunkAssets
Phenomic includes webpack itself and sets up part of the config. You can run a build using Phenomic and it will also take custom webpack settings from your own generate project. A default project is created for you to modify when you initialise Phenomic.
I've tried changing the version numbers to "webpack": "2.1.0-beta.13", under Phenomic's peer and normal dependencies and rebuilding with it npm linked. I also made a few of the changes needed for updating webpack 1 to version 2.
I've also deleted node_modules in both Phenomic and my project directories, which did not seem to help (and took a long time ;).
I've browsed through this thread which was webpack 1 related and there is some suggestion of dependencies causing multiple copies of webpack. Any ideas are appreciated.
Update:
I made my webpack 2 changes in Phenomic and setup the default project. It seems to build (with some CSS issues), so the problem seems related to the more complex project I am using Phenomic with. Maybe another dependency is bringing in another copy of webpack.
It seems this is npm link related as I installed installed Phenomic from my file system and the issue disappears.
I also noticed there was a global copy of Phenomic, which is also possibly related to npm link.
Another tip I found was npm ls is useful finding what dependencies are in use. You can pipe the output to a file if you want to read it in an editor.
I've tried a few times to install my first AngularJS project via their docs:
https://docs.angularjs.org/misc/contribute
*# Clone your Github repository:
git clone "git#github.com:<github username>/angular.js.git"
# Go to the AngularJS directory:
cd angular.js
# Add the main AngularJS repository as an upstream remote to your repository:
git remote add upstream "https://github.com/angular/angular.js.git"
# Install node.js dependencies:
npm install
# Install bower components:
bower install
# Build AngularJS:
grunt package*
Each time I try to npm install it returns an error for jasmine-node
I've searched for solutions and tried a bunch of methods & hopeful tests but still not receiving back any luck.
Much appreciated for any help, guys!
Those docs are for people who want to contribute (work on angularjs library) and not for people who are building projects using angular. To me, it seems that you'd want the latter.
There are plenty of tutorials out there, just search for angularjs beginner tutorial, and find the one that suits you the most.
An issue I was frequently experiencing was protocol issues due to npm errors being returned especially for Bower.
You can make git replace the protocol for you. Just run:
git config --global url."https://".insteadOf git://
Apologies if this thread is a bit of a mess, but hope it helps someone out there too.