CODEWITHSUNDEEP
node.jsmeteor
A. S.
A. S.

Reputation: 153

Packages that are not updated when running meteor

I alter some code in a package at

C:\Users\usr\AppData\Local\.meteor\packages\accounts-ui-unstyled\1.3.0\web.browser\login_buttons.js

The thing is , after I alter the code and run “meteor” in the command line the changes are not implemented, I even deleted the whole package mentioned before and run the app and it was like … nothing happened, it’s like the application have some sort of a cache of the packages that he doesn’t have to go to that path to get them , instead it uses what it had from it before. Can anyone please explain this to me ? What’s happening here ?

Upvotes: 0

Views: 46

Answers (1)

Jankapunkt
Jankapunkt

Reputation: 8413

The correct way of "changing" a package is to git clone the package from git (or otherwise retrieve it's source) into either a project internal /packages folder or a project external folder (requires environment variable METOER_PACKAGE_DIRS).

If the package is, as in your case, a Meteor internal package, you can also copy only the package into your project and even add it to your versioning.

In this package you then apply your changes. It will be used in favor of the atmosphere package.

A good practice is to also increment the package version, so it is known for everyone that a custom version is in use.

Why you should not change packages inside the users \Users\...\.meteor installation packages folder?

This is the path to packages, that will be used as defaults for every new meteor project you create. Deep changes can create deep damage to your projects since changing a package will apply to all dependent projects.

Think also about project specific customization. The above described method will allow this, too.

Upvotes: 1

Related Questions