Chore: don't create the npm-artifacts dir since yarn packages:pack does this… (#62246)

* don't create the npm-artifacts dir since yarn packages:pack does this already

* fix an any to trigger a canary build
This commit is contained in:
Ashley Harrison 2023-01-26 16:41:08 +00:00 committed by GitHub
parent 284ca4eab4
commit a344c88a01
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 2 additions and 7 deletions

View File

@ -1,11 +1,10 @@
import { ArrayVector, FieldType } from '@grafana/data';
import { ArrayVector, EventBus, FieldType } from '@grafana/data';
import { getTheme } from '@grafana/ui';
import { preparePlotConfigBuilder } from './utils';
describe('when fill below to option is used', () => {
// eslint-disable-next-line
let eventBus: any;
let eventBus: EventBus;
// eslint-disable-next-line
let renderers: any[];
// eslint-disable-next-line

View File

@ -15,10 +15,6 @@ else
echo "//registry.npmjs.org/:_authToken=${NPM_TOKEN}" >> ~/.npmrc
if [ ! -d './npm-artifacts' ]; then
mkdir './npm-artifacts'
fi
echo $'\nPacking packages'
yarn packages:pack