Bitsrc eject component if there is no update to export
up vote
1
down vote
favorite
I'm using Bitsrc.io to manage shared components.
Sometimes it happens that I import a remote component which adds the physical files to my project.
I then want to eject the module so that it is managed by npm again.
However I haven't made any changes so bit-cli responds with
nothing to export
On their docs site I cannot find another reference to using the --eject flag except with the export command.
Anyone bumped into this before?
javascript npm bit-src
add a comment |
up vote
1
down vote
favorite
I'm using Bitsrc.io to manage shared components.
Sometimes it happens that I import a remote component which adds the physical files to my project.
I then want to eject the module so that it is managed by npm again.
However I haven't made any changes so bit-cli responds with
nothing to export
On their docs site I cannot find another reference to using the --eject flag except with the export command.
Anyone bumped into this before?
javascript npm bit-src
add a comment |
up vote
1
down vote
favorite
up vote
1
down vote
favorite
I'm using Bitsrc.io to manage shared components.
Sometimes it happens that I import a remote component which adds the physical files to my project.
I then want to eject the module so that it is managed by npm again.
However I haven't made any changes so bit-cli responds with
nothing to export
On their docs site I cannot find another reference to using the --eject flag except with the export command.
Anyone bumped into this before?
javascript npm bit-src
I'm using Bitsrc.io to manage shared components.
Sometimes it happens that I import a remote component which adds the physical files to my project.
I then want to eject the module so that it is managed by npm again.
However I haven't made any changes so bit-cli responds with
nothing to export
On their docs site I cannot find another reference to using the --eject flag except with the export command.
Anyone bumped into this before?
javascript npm bit-src
javascript npm bit-src
asked Nov 11 at 12:24
Patrick Geyer
840825
840825
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
2
down vote
Right now in order to achieve this you need to run the following commands:
bit remove id
npm install id-npm
(*) - look in the bitsrc ui as they way id looks like in bit registry is different from npm.
if you do make changes you can do bit export --eject
which will do remove and npm install. This command is currently being developed in the dev branch and is probably going to be available in the next release. You can also force an export if you force a tag by using --all flag or --scope. I advice against it.
an independent `ejecta command is coming soon github.com/teambit/bit/pull/1240
– itaymendel
Nov 13 at 8:50
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
2
down vote
Right now in order to achieve this you need to run the following commands:
bit remove id
npm install id-npm
(*) - look in the bitsrc ui as they way id looks like in bit registry is different from npm.
if you do make changes you can do bit export --eject
which will do remove and npm install. This command is currently being developed in the dev branch and is probably going to be available in the next release. You can also force an export if you force a tag by using --all flag or --scope. I advice against it.
an independent `ejecta command is coming soon github.com/teambit/bit/pull/1240
– itaymendel
Nov 13 at 8:50
add a comment |
up vote
2
down vote
Right now in order to achieve this you need to run the following commands:
bit remove id
npm install id-npm
(*) - look in the bitsrc ui as they way id looks like in bit registry is different from npm.
if you do make changes you can do bit export --eject
which will do remove and npm install. This command is currently being developed in the dev branch and is probably going to be available in the next release. You can also force an export if you force a tag by using --all flag or --scope. I advice against it.
an independent `ejecta command is coming soon github.com/teambit/bit/pull/1240
– itaymendel
Nov 13 at 8:50
add a comment |
up vote
2
down vote
up vote
2
down vote
Right now in order to achieve this you need to run the following commands:
bit remove id
npm install id-npm
(*) - look in the bitsrc ui as they way id looks like in bit registry is different from npm.
if you do make changes you can do bit export --eject
which will do remove and npm install. This command is currently being developed in the dev branch and is probably going to be available in the next release. You can also force an export if you force a tag by using --all flag or --scope. I advice against it.
Right now in order to achieve this you need to run the following commands:
bit remove id
npm install id-npm
(*) - look in the bitsrc ui as they way id looks like in bit registry is different from npm.
if you do make changes you can do bit export --eject
which will do remove and npm install. This command is currently being developed in the dev branch and is probably going to be available in the next release. You can also force an export if you force a tag by using --all flag or --scope. I advice against it.
answered Nov 12 at 12:48
qballer
1,2181333
1,2181333
an independent `ejecta command is coming soon github.com/teambit/bit/pull/1240
– itaymendel
Nov 13 at 8:50
add a comment |
an independent `ejecta command is coming soon github.com/teambit/bit/pull/1240
– itaymendel
Nov 13 at 8:50
an independent `ejecta command is coming soon github.com/teambit/bit/pull/1240
– itaymendel
Nov 13 at 8:50
an independent `ejecta command is coming soon github.com/teambit/bit/pull/1240
– itaymendel
Nov 13 at 8:50
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53248728%2fbitsrc-eject-component-if-there-is-no-update-to-export%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown