Deploy edited npm package
I have installed npm package ngx-cookie-service
I have also changed code in node_module > ngx-cookie-service folder this works fine on local host but when I deployed my angular app to azure, these changes not working.
How to make it work on server?
angular 
azure npm node-modules edited Jan 2 at 12:40
Bharat
2,19911836
asked Jan 2 at 9:17
FaisalFaisal
114118
add a comment |
I have installed npm package ngx-cookie-service
I have also changed code in node_module > ngx-cookie-service folder this works fine on local host but when I deployed my angular app to azure, these changes not working.
How to make it work on server?
angular azure npm node-modules edited Jan 2 at 12:40
Bharat
2,19911836
asked Jan 2 at 9:17
FaisalFaisal
114118
Did you try install the package in Kudu and change the code as you did in your local.
– George Chen
Jan 2 at 9:43
How are you building/deploying your application? If you are building it locally usingng build, then the built app will respect your local changes to node_modules. If you are building something serverside, it's likely doing an npm/yarn install before building it - which won't have your local changes. Your best bet is to either subsume the logic in to your actual application, or if this is really not an option, fork the npm package and re-publish your own.
– hevans900
Jan 2 at 16:51
add a comment |
I have installed npm package ngx-cookie-service
I have also changed code in node_module > ngx-cookie-service folder this works fine on local host but when I deployed my angular app to azure, these changes not working.
How to make it work on server?
angular azure npm node-modules edited Jan 2 at 12:40
Bharat
2,19911836
asked Jan 2 at 9:17
FaisalFaisal
114118
I have installed npm package ngx-cookie-service
I have also changed code in node_module > ngx-cookie-service folder this works fine on local host but when I deployed my angular app to azure, these changes not working.
How to make it work on server?
angular azure npm node-modules angular azure npm node-modules edited Jan 2 at 12:40
Bharat
2,19911836
asked Jan 2 at 9:17
FaisalFaisal
114118
edited Jan 2 at 12:40
Bharat
2,19911836
asked Jan 2 at 9:17
FaisalFaisal
114118
edited Jan 2 at 12:40
Bharat
2,19911836
edited Jan 2 at 12:40
Bharat
2,19911836
edited Jan 2 at 12:40
Bharat
2,19911836
2,19911836
asked Jan 2 at 9:17
FaisalFaisal
114118
asked Jan 2 at 9:17
FaisalFaisal
114118
asked Jan 2 at 9:17
FaisalFaisal
114118
114118
Did you try install the package in Kudu and change the code as you did in your local.
– George Chen
Jan 2 at 9:43
How are you building/deploying your application? If you are building it locally usingng build, then the built app will respect your local changes to node_modules. If you are building something serverside, it's likely doing an npm/yarn install before building it - which won't have your local changes. Your best bet is to either subsume the logic in to your actual application, or if this is really not an option, fork the npm package and re-publish your own.
– hevans900
Jan 2 at 16:51
add a comment |
Did you try install the package in Kudu and change the code as you did in your local.
– George Chen
Jan 2 at 9:43
How are you building/deploying your application? If you are building it locally usingng build, then the built app will respect your local changes to node_modules. If you are building something serverside, it's likely doing an npm/yarn install before building it - which won't have your local changes. Your best bet is to either subsume the logic in to your actual application, or if this is really not an option, fork the npm package and re-publish your own.
– hevans900
Jan 2 at 16:51
Did you try install the package in Kudu and change the code as you did in your local.
– George Chen
Jan 2 at 9:43
Did you try install the package in Kudu and change the code as you did in your local.
– George Chen
Jan 2 at 9:43
How are you building/deploying your application? If you are building it locally using
ng build, then the built app will respect your local changes to node_modules. If you are building something serverside, it's likely doing an npm/yarn install before building it - which won't have your local changes. Your best bet is to either subsume the logic in to your actual application, or if this is really not an option, fork the npm package and re-publish your own.– hevans900
Jan 2 at 16:51
How are you building/deploying your application? If you are building it locally using
ng build, then the built app will respect your local changes to node_modules. If you are building something serverside, it's likely doing an npm/yarn install before building it - which won't have your local changes. Your best bet is to either subsume the logic in to your actual application, or if this is really not an option, fork the npm package and re-publish your own.– hevans900
Jan 2 at 16:51
add a comment |
1 Answer
1
active
oldest
votes
Since when your app works fine on local, there are two ways to make it work on Azure WebApp.
Just directly upload all files and directories of your project to Azure and configure the
web.configfile to make it work as same as on local. You can refer to the offical documentsCreate a Node.js web app in AzureandDeploy your app to Azure App Service with a ZIP or WAR fileto create a zip file of your project, or directly upload all to thewwwrootpath of Kudo Console, which must includesnode_moduledirectory and even excludespackage.jsonto avoid automatically update your changes forngx-cookie-service, then to configureweb.configlikeBest practices and troubleshooting guide for node applications on Azure App Service WindowsandUsing a custom web.config for Node appssaid. It's the simplest way manually.As @hevans900 said, you can create a new NPM package for your changed
ngx-cookie-serviceto publish to public hub, and reference it in your project to rebuild and redeploy.
answered Jan 18 at 6:16
Peter PanPeter Pan
11.8k3824
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%2f54003804%2fdeploy-edited-npm-package%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
Since when your app works fine on local, there are two ways to make it work on Azure WebApp.
Just directly upload all files and directories of your project to Azure and configure the
web.configfile to make it work as same as on local. You can refer to the offical documentsCreate a Node.js web app in AzureandDeploy your app to Azure App Service with a ZIP or WAR fileto create a zip file of your project, or directly upload all to thewwwrootpath of Kudo Console, which must includesnode_moduledirectory and even excludespackage.jsonto avoid automatically update your changes forngx-cookie-service, then to configureweb.configlikeBest practices and troubleshooting guide for node applications on Azure App Service WindowsandUsing a custom web.config for Node appssaid. It's the simplest way manually.As @hevans900 said, you can create a new NPM package for your changed
ngx-cookie-serviceto publish to public hub, and reference it in your project to rebuild and redeploy.
answered Jan 18 at 6:16
Peter PanPeter Pan
11.8k3824
add a comment |
Since when your app works fine on local, there are two ways to make it work on Azure WebApp.
Just directly upload all files and directories of your project to Azure and configure the
web.configfile to make it work as same as on local. You can refer to the offical documentsCreate a Node.js web app in AzureandDeploy your app to Azure App Service with a ZIP or WAR fileto create a zip file of your project, or directly upload all to thewwwrootpath of Kudo Console, which must includesnode_moduledirectory and even excludespackage.jsonto avoid automatically update your changes forngx-cookie-service, then to configureweb.configlikeBest practices and troubleshooting guide for node applications on Azure App Service WindowsandUsing a custom web.config for Node appssaid. It's the simplest way manually.As @hevans900 said, you can create a new NPM package for your changed
ngx-cookie-serviceto publish to public hub, and reference it in your project to rebuild and redeploy.
answered Jan 18 at 6:16
Peter PanPeter Pan
11.8k3824
add a comment |
Since when your app works fine on local, there are two ways to make it work on Azure WebApp.
Just directly upload all files and directories of your project to Azure and configure the
web.configfile to make it work as same as on local. You can refer to the offical documentsCreate a Node.js web app in AzureandDeploy your app to Azure App Service with a ZIP or WAR fileto create a zip file of your project, or directly upload all to thewwwrootpath of Kudo Console, which must includesnode_moduledirectory and even excludespackage.jsonto avoid automatically update your changes forngx-cookie-service, then to configureweb.configlikeBest practices and troubleshooting guide for node applications on Azure App Service WindowsandUsing a custom web.config for Node appssaid. It's the simplest way manually.As @hevans900 said, you can create a new NPM package for your changed
ngx-cookie-serviceto publish to public hub, and reference it in your project to rebuild and redeploy.
answered Jan 18 at 6:16
Peter PanPeter Pan
11.8k3824
Since when your app works fine on local, there are two ways to make it work on Azure WebApp.
Just directly upload all files and directories of your project to Azure and configure the
web.configfile to make it work as same as on local. You can refer to the offical documentsCreate a Node.js web app in AzureandDeploy your app to Azure App Service with a ZIP or WAR fileto create a zip file of your project, or directly upload all to thewwwrootpath of Kudo Console, which must includesnode_moduledirectory and even excludespackage.jsonto avoid automatically update your changes forngx-cookie-service, then to configureweb.configlikeBest practices and troubleshooting guide for node applications on Azure App Service WindowsandUsing a custom web.config for Node appssaid. It's the simplest way manually.As @hevans900 said, you can create a new NPM package for your changed
ngx-cookie-serviceto publish to public hub, and reference it in your project to rebuild and redeploy.
answered Jan 18 at 6:16
Peter PanPeter Pan
11.8k3824
answered Jan 18 at 6:16
Peter PanPeter Pan
11.8k3824
answered Jan 18 at 6:16
Peter PanPeter Pan
11.8k3824
answered Jan 18 at 6:16
Peter PanPeter Pan
11.8k3824
11.8k3824
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%2f54003804%2fdeploy-edited-npm-package%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
Did you try install the package in Kudu and change the code as you did in your local.
– George Chen
Jan 2 at 9:43
How are you building/deploying your application? If you are building it locally using
ng build, then the built app will respect your local changes to node_modules. If you are building something serverside, it's likely doing an npm/yarn install before building it - which won't have your local changes. Your best bet is to either subsume the logic in to your actual application, or if this is really not an option, fork the npm package and re-publish your own.– hevans900
Jan 2 at 16:51