$ bit import bit.envs/testers/jest
failed running npm install at /Users/ran/Projects/ui-platform-utils/envs/components/testers/jest
npm ERR! code E404
npm ERR! 404 Not Found - GET https://registry.npmjs.org/@bit%2fbit.utils.validation.empty - Not found
npm ERR! 404
npm ERR! 404 '@bit/bit.utils.validation.empty@0.0.1' is not in the npm registry.
npm ERR! 404 You should bug the author to publish it (or use the name yourself!)
npm ERR! 404 It was specified as a dependency of 'jest'
npm ERR! 404
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.
npm ERR! A complete log of this run can be found in:
npm ERR! /Users/ran/.npm/_logs/2020-02-06T10_50_53_789Z-debug.log
see troubleshooting at https://docs.bit.dev/docs/installing-components
run 'bit doctor' to get detailed workspace diagnosis and issue resolution.
A while ago we've migrated the chat to Slack. Please join here to continue the conversation.
npm i issue, you need to configure your .npmrc file to connect have your client configured to bit @bit registry. see here for more information.
Looks like to use Bit, I need to buy into it's module specifier conventions. Can this be avoided? Suppose each project (which is a submodule in my umbrella repo) contains web components, and I want to share them across projects (some projects are apps, some are libs).
Does bit make it easy to use only Node.js-style import specifiers and store everything on NPMjs.com?
Ah, I see, Bit calls them "workspaces". So then, in my case, I am looking to have an "umbrella repo" with a bunch of Bit "workspaces" as git submodules. Would this work?
Basically, I'd like a big "umbrella repo" to house all my related apps and libs as git submodules.
bit init in each workspace (git submodule). Now I'm wondering if this can be done automatically across all "workspaces".
bit.dev?
hi @trusktr , we've moved to a slack community and left gitter a few weeks ago.
https://join.slack.com/t/bit-dev-community/shared_invite/enQtNzM2NzQ3MTQzMTg3LWI2YmFmZjQwMTkxNmFmNTVkYzU2MGI2YjgwMmJlZDdkNWVhOGIzZDFlYjg4MGRmOTM4ODAxNTIxMTMwNWVhMzg
As for your questions, BIt is designed to handle smaller components, and not for projects.
Usually, teams use lerna/rush to manage a small number of large projects in the same repository. On the other hand, Bit is designed to manage many small "projects" (modules/components) in the same workspace. technically it's possible to manage larger projects, but it is not optimized for it. Bit is optimized for projects with a relatively small amount of code and a lot of dependencies.
it's possible to group together several Bit workspaces, each with its own set of components, in the same "master" workspace.
as for sharing components to npmjs, it's possible, but you'll need to implement an extension to do just that. it's also possible to change the default @bit, but this is not supported when hosting code on bit.dev .
@itaymendel_twitter Cool! Thanks for that info. Seems that Bit can be paired with Lerna/Rush. F.e. I can use Lerna to run test commands across multiple repos, and the test commands can trigger Bit commands in each of the projects.
What about symlinking dependencies for development? Suppose I want to edit code for a component and see the changes in multiple projects at once? Normally Lerna cross links dependencies, or we can manually link local projects into dependents the old npm link way, and test changes across them all at once. Does bit have such feature for developing a component and testing it across across multiple projects at once?
we have moved to Slack
https://join.slack.com/t/bit-dev-community/shared_invite/enQtNzM2NzQ3MTQzMTg3LWI2YmFmZjQwMTkxNmFmNTVkYzU2MGI2YjgwMmJlZDdkNWVhOGIzZDFlYjg4MGRmOTM4ODAxNTIxMTMwNWVhMzg
error: bit failed to build app with the following exception:
Command failed with exit code 1 (EPERM): npm install --no-save
Error: Command failed with exit code 1 (EPERM): npm install --no-save
Hello, sorry for invading your privacy
Please I will appreciate if you read
I am Logan Dexter from Netherlands
I want to introduce you to a money making opportunity. Its a bitcoin trading company that helps you generate profit through trading cryptocurrency
It’s a highly profitable investment platform, it helps you trade and generate profits and then send it to your account daily. You will be able to earn 10% of your investment daily for up to 30 days and you also get your principal
I know it sounds too good to be true, I understand because I also felt like that when I first met them but now am fully convinced that it’s all true because I have earned up to $5000 with them.
You can also earn 5% in referral bonus if you don’t have capital, All you need to do is refer someone and you can also earn. As am doing now
It doesn’t require much of your time, all you need to do is register and deposit and you will start earning daily
If you don’t know anything about bitcoin you can also text me on Whatsaap so I will educate you more.
Visit http://Ftxfutures.io//?ref=Logan
Or chat me on Whatsaap for more explanation https://wa.me/message/3GUAIPJFDS5KJ1
Hi all. I'm new to bit.dev. I would like to create a custom npm cli tool and host it on bit.dev for distribution. My question is: suppose I have created a nodejs project, with a (trimmed down) package.json:
{
"name": "xxx",
...
"main": "./dist/plopfile.js",
"scripts": {
"plop": "plop --plopfile ./dist/plopfile.js"
},
"bin": {
"my-plop": "./dist/index.js" },
...
"devDependencies": {
...
},
"dependencies": {
...
}
}On the root of the project, I've created an index.js file with the #!/usr/bin/env node instruction.
How do I go about deploying this tool with bit.dev? Do I create just a component with all required files (package.json, index.js) and then when I import this component in a new project, can I run it as a script command? In other words is it possible to deploy a normal npm cli with bit.dev?
Thanks for your assistance.
Hello, I am investigating using bit.dev for our new front end project and I am trying to understand how best to integrate with next.js. I am thinking of using the following project structure. Does this make sense? I haven't been able to find any documentation on how integration with next.js. Should I be using the bit.dev Application component somehow to start the next.js app? Given it requires starting with command "next dev".
prototype-microfrontend-submodules
├── node_modules
├── packages
│ ├── nextjs-shared // the components in this sub-repo will be exported to bit cloud under a nextjs-shared scope
│ ├── nextjs-shell-webapp // this is a Next.js web app that federates remotes from micro frontends (i.e. nextjs-ssg-webapp and nextjs-ssr-webapp) using module federation
│ ├── nextjs-ssg-webapp (/nextjs_ssg) // this is a Next.js web app that contains Page components, where each Page fetches data, stores it in the redux store and passes it to components that are imported from bit cloud, it also contains components that are specific to this micro frontend domain that are exported to bit cloud under a nextjs-ssg-webapp scope
│ ├── nextjs-ssr-webapp (/nextjs_ssr) // this is a Next.js web app that contains Page components, where each Page fetches data, stores it in the redux store and passes it to components that are imported from bit cloud, it also contains components that are specific to this micro frontend domain that are exported to bit cloud under a nextjs-ssr-webapp scope
│ └── reactjs-shared // the components in this sub-repo will be exported to bit cloud under a reactjs-shared scope
├── .npmrc
├── package.json
├── README.md
├── yarn.lock
└── .npmrc
if you are targeting a self-hosted scope, please ensure the scope is configured in your remotes (via "bit remote" command) and that the scope name is correct.
if this is a scope on bit.cloud please add the organization name before the scope (yourOrg.some-scope-name)