More info on setting up local plugins #1868
-
|
I'm trying to write a plugin and hook it up to auto locally, my plugins field in the but auto keeps logging a warning saying it can't find the plugin. That path is relative to where Is there something I'm doing obviously wrong? I've played around with different paths and they all result in the log saying it can't find the plugin. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 8 replies
-
|
Are you using the npm version or the bundled version? |
Beta Was this translation helpful? Give feedback.
-
|
It does say that if found the plugin. You should be able to see these same logs when running auto during a release using |
Beta Was this translation helpful? Give feedback.
-
|
This is what we got from a normal release workflow. Merged a dependabot PR. If it helps this is our release workflow name: Release
on: [push]
jobs:
release:
name: Release
runs-on: ubuntu-latest
steps:
- name: Checkout Repo
uses: actions/checkout@v2
with:
token: ${{ secrets.GH_TOKEN }}
- name: Prepare repository
run: git fetch --unshallow --tags
- name: Setup Node.js
uses: actions/setup-node@v2
with:
node-version: 12.x
- name: Cache node modules
uses: actions/cache@v2.1.4
with:
path: node_modules
key: yarn-deps-${{ hashFiles('yarn.lock') }}
restore-keys: |
yarn-deps-${{ hashFiles('yarn.lock') }}
- name: Create Release
env:
GITHUB_TOKEN: ${{ secrets.GH_TOKEN }}
run: |
yarn install --frozen-lockfile
yarn build
npx auto shipit -vv |
Beta Was this translation helpful? Give feedback.
-
|
It looks like a dep is missing in for your plugin I'm guessing you ran I can also take a look at the repo |
Beta Was this translation helpful? Give feedback.
-
|
Yeah looking into it it's obvious now, we are not packaging our plugin correctly just running |
Beta Was this translation helpful? Give feedback.
-
|
I'm always up for documentation contributions 😄 |
Beta Was this translation helpful? Give feedback.
Are you using the npm version or the bundled version?