# Removing a plugin

Installing plugin in Capacitor is a little different from Cordova. Since Cordova considers the platform code as build time asset, it compiles the platform every time a build is made.

Capacitor works differently. It compiles the platforms once, and further changes can be simply copied into the platforms using `npx cap sync` 

Plugins are installed as `npm` or `yarn` package in Capacitor. Hence, to remove them, 

* You will have to remove the package from `package.json` and also remove it from `node_modules` using `npm uninstall <packageName>`
* In case the package has already been copied to platforms, you will have to "undo" all the steps you did when attaching those packages / plugins to the platforms. \
  E.g. When implementing Facebook Login in Capacitor, as detailed in our [tutorial here](https://enappd.com/blog/facebook-login-in-ionic-react-capacitor-apps/118), You need to make few modifications in Android project using Android Studio

There are changes done in  `android/app/src/main/java/**/**/MainActivity.java`, `android/app/src/main/AndroidManifest.xml` and `android/app/src/main/res/values/strings.xml` . All these changes need to be undone to remove all traces of the package from the project.

Check the details in our detailed [tutorial here](https://enappd.com/blog/facebook-login-in-ionic-react-capacitor-apps/118) for Facebook Login Plugin.  A similar process will be needed for other plugins as well.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://enappd.gitbook.io/capacitor-full-app-ionic-angular/removing-a-plugin.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.