teambit / bit-with-github-actions Goto Github PK

Hi there!

I was wondering how to specify the nature of our changes on the components.

Using bit tag -a doesn't seem to ba a solution to this. In my company we are currently using Lerna with conventional commits.

Is conventional commits something you are planning to integrate to make the versioning process usable?

Hi, I am trying to install my @bit public components on a project that is in a subfolder (frontend/) but I am getting the following error:

npm ERR! code E404
npm ERR! 404 Not Found - GET https://registry.npmjs.org/@mattborghi%2fsciquant.ui.github - Not found
npm ERR! 404 
npm ERR! 404  '@mattborghi/[email protected]' is not in the npm registry.

I tried moving the .npmrc file into the subfolder but the error persists. The yml file that I used is this one

name: Deploy to Github Pages
on: 
  push:
    branches: 
      - 'main'
jobs:
  Deploy:
    runs-on: ubuntu-latest
    defaults:
      run:
        working-directory: ./frontend
    steps:
      - uses: actions/checkout@v2
      - uses: actions/setup-node@v2
        with:
          node-version: '14.x'
      - run: npm install
      - run: npm run deploy

I also tried setting this configuration without using the .npmrc file with no luck like this

- uses: actions/setup-node@v2
        with:
          always-auth: true
          node-version: '14.x'
          registry-url: https://node.bit.dev

I get another error in this case

npm WARN audit Audit result from registry missing metadata. This is probably an issue with the registry.
added 2060 packages from 1143 contributors in 49.193s

147 packages are looking for funding
  run `npm fund` for details

npm ERR! Cannot convert undefined or null to object

Does anyone have any idea why this might be happening? Thanks in advance, Matias.