All geek questions in one place

Location of the local Meteor 0.9 package

I noticed that my recently created Meteor 0.9 project is missing a package package. This means that he should use a package of ~/.meteor things. However, I cannot work the way I jump between machines all day, and I would like the package to stay in place; as in the project folder itself.

In the previous Meteor 0.8.3 project, I manually created a folder with packages in the project, and when I add the package, it got there (for example, I can find collectionFs inside the package / in the project directory).

I want this to be so. How can I do this safely?

+5
source share
3 answers

You can still package packages in the top-level package directory inside your project, and then run meteor add as usual. These packages are simply considered application specific packages. Below are documents about using packages. The corresponding bit is quoted here:

In addition to the Meteor official release packages used by your application, a list of meteorites and meteorites also adds a search to the package directory at the top of the application.

+6
source

I think the idea was to distinguish the stand-alone application code from third-party libraries. As the author of the package, this means that there are fewer forks in my library in my library where small changes float in the Atmosphere. It also makes your applications a little less error prone (given that the packages are stable) and encourages better package maintenance.

If you want to use local packages, here is a good walkthrough .

For NPM packages, also check meteorhacks:npm | github

+1
source

For the FS collection, you must use meteor 0.6. You must add a new meteor 0.6 release file. https://github.com/CollectionFS/Meteor-cfs-example-filemanager

0
source

Source: https://habr.com/ru/post/1204608/

More articles:


All Articles