Documentation in webpack template for installed in buildfiresdk
I am trying to create a app with the buildfiresdk. I generated a buildfire plugin using the "buildfire plugin init webpack" command, however I am not sure how to edit this template to make it my own. Could anyone point me to a documentation that helps with this issue.
javascript webpack buildfire
asked Nov 23 '18 at 16:51
Symo1Symo1
12
add a comment |
I am trying to create a app with the buildfiresdk. I generated a buildfire plugin using the "buildfire plugin init webpack" command, however I am not sure how to edit this template to make it my own. Could anyone point me to a documentation that helps with this issue.
javascript webpack buildfire
asked Nov 23 '18 at 16:51
Symo1Symo1
12
add a comment |
I am trying to create a app with the buildfiresdk. I generated a buildfire plugin using the "buildfire plugin init webpack" command, however I am not sure how to edit this template to make it my own. Could anyone point me to a documentation that helps with this issue.
javascript webpack buildfire
asked Nov 23 '18 at 16:51
Symo1Symo1
12
I am trying to create a app with the buildfiresdk. I generated a buildfire plugin using the "buildfire plugin init webpack" command, however I am not sure how to edit this template to make it my own. Could anyone point me to a documentation that helps with this issue.
javascript webpack buildfire
javascript webpack buildfire
asked Nov 23 '18 at 16:51
Symo1Symo1
12
asked Nov 23 '18 at 16:51
Symo1Symo1
12
asked Nov 23 '18 at 16:51
Symo1Symo1
12
asked Nov 23 '18 at 16:51
Symo1Symo1
12
asked Nov 23 '18 at 16:51
Symo1Symo1
12
12
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
You should see 2 folders on the root of the plugin folder:
- webpack: Responsible for all your webpack settings. You may not need to change anything.
- src: This is where all your plugin source code is at. You will be making the majority of your changes here.
This template has some dependencies. So you want to navigate through the CLI to the root of the plugin and then execute npm install this will then install all that is needed.
Once the dependencies are installed. You can now run webpack to auto bundle changes for you on the fly by executing npm start at the root of the plugin.
You should be ready to start the SDK now. Simply open a separate terminal window. Then navigate to the root of the SDK and execute buildfire run
You should be good to go.
answered Nov 26 '18 at 17:04
Daniel_MadainDaniel_Madain
29119
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
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%2f53450431%2fdocumentation-in-webpack-template-for-installed-in-buildfiresdk%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
You should see 2 folders on the root of the plugin folder:
- webpack: Responsible for all your webpack settings. You may not need to change anything.
- src: This is where all your plugin source code is at. You will be making the majority of your changes here.
This template has some dependencies. So you want to navigate through the CLI to the root of the plugin and then execute npm install this will then install all that is needed.
Once the dependencies are installed. You can now run webpack to auto bundle changes for you on the fly by executing npm start at the root of the plugin.
You should be ready to start the SDK now. Simply open a separate terminal window. Then navigate to the root of the SDK and execute buildfire run
You should be good to go.
answered Nov 26 '18 at 17:04
Daniel_MadainDaniel_Madain
29119
add a comment |
You should see 2 folders on the root of the plugin folder:
- webpack: Responsible for all your webpack settings. You may not need to change anything.
- src: This is where all your plugin source code is at. You will be making the majority of your changes here.
This template has some dependencies. So you want to navigate through the CLI to the root of the plugin and then execute npm install this will then install all that is needed.
Once the dependencies are installed. You can now run webpack to auto bundle changes for you on the fly by executing npm start at the root of the plugin.
You should be ready to start the SDK now. Simply open a separate terminal window. Then navigate to the root of the SDK and execute buildfire run
You should be good to go.
answered Nov 26 '18 at 17:04
Daniel_MadainDaniel_Madain
29119
add a comment |
You should see 2 folders on the root of the plugin folder:
- webpack: Responsible for all your webpack settings. You may not need to change anything.
- src: This is where all your plugin source code is at. You will be making the majority of your changes here.
This template has some dependencies. So you want to navigate through the CLI to the root of the plugin and then execute npm install this will then install all that is needed.
Once the dependencies are installed. You can now run webpack to auto bundle changes for you on the fly by executing npm start at the root of the plugin.
You should be ready to start the SDK now. Simply open a separate terminal window. Then navigate to the root of the SDK and execute buildfire run
You should be good to go.
answered Nov 26 '18 at 17:04
Daniel_MadainDaniel_Madain
29119
You should see 2 folders on the root of the plugin folder:
- webpack: Responsible for all your webpack settings. You may not need to change anything.
- src: This is where all your plugin source code is at. You will be making the majority of your changes here.
This template has some dependencies. So you want to navigate through the CLI to the root of the plugin and then execute npm install this will then install all that is needed.
Once the dependencies are installed. You can now run webpack to auto bundle changes for you on the fly by executing npm start at the root of the plugin.
You should be ready to start the SDK now. Simply open a separate terminal window. Then navigate to the root of the SDK and execute buildfire run
You should be good to go.
answered Nov 26 '18 at 17:04
Daniel_MadainDaniel_Madain
29119
answered Nov 26 '18 at 17:04
Daniel_MadainDaniel_Madain
29119
answered Nov 26 '18 at 17:04
Daniel_MadainDaniel_Madain
29119
answered Nov 26 '18 at 17:04
Daniel_MadainDaniel_Madain
29119
29119
add a comment |
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.
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%2f53450431%2fdocumentation-in-webpack-template-for-installed-in-buildfiresdk%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
