forked from tornado-packages/archive-monorepo
32 lines
1.6 KiB
YAML
32 lines
1.6 KiB
YAML
|
# So basically, we want to selectively download packages from the Gitea repository but still allow the
|
||
|
|
# main repositories, so we are going to have to scope our packages properly.
|
||
|
|
npmScopes:
|
||
|
|
tornado:
|
||
|
|
# The @tornado scope can just be set to the right registry by editing the T-Hax here.
|
||
|
|
# I could even make it an env var but it seems too much, that is for secrets.
|
||
|
|
npmPublishRegistry: "https://development.tornadocash.community/api/packages/T-Hax/npm/"
|
||
|
|
npmRegistryServer: "https://development.tornadocash.community/api/packages/T-Hax/npm/"
|
||
|
|
# The below can be EXPORTED via some env file which actually exports the variables though
|
||
|
|
# Check the env.example, you will notice it's not a regular env
|
||
|
|
# So split your env files up, since this is only for manual actions
|
||
|
|
npmAuthToken: ${GITEA_AUTH_TOKEN}
|
||
|
|
|
||
|
|
# If the following isn't set you won't have a node_modules folder
|
||
|
|
# You might be used to a node_modules folder instead of a pnp or other folder type
|
||
|
|
# If you want to use the new linkers uncomment or change the following
|
||
|
|
nodeLinker: "node-modules"
|
||
|
|
|
||
|
|
# So the tornadocash org, the person who maintains it, might setup something (in future) like,
|
||
|
|
# tornadocash:
|
||
|
|
# npmPublishRegistry: "https://development.tornadocash.community/api/packages/tornadocash/npm/"
|
||
|
|
# npmRegistryServer: "https://development.tornadocash.community/api/packages/tornadocash/npm/"
|
||
|
|
|
||
|
|
# We disable telemetry for obvious reasons. enableTelemetry: false
|
||
|
|
enableTelemetry: false
|
||
|
|
|
||
|
|
plugins:
|
||
|
|
- path: .yarn/plugins/@yarnpkg/plugin-workspace-tools.cjs
|
||
|
|
spec: "@yarnpkg/plugin-workspace-tools"
|
||
|
|
|
||
|
|
npmPublishAccess: public
|