Customize webpack DevServer message
Currently, when I start my Webpack DevServer, it outputs this message:
i 「wds」: Project is running at http://localhost:8080/
Is it possible to somehow customize the url in message to my current project path, which is in my case: http://localhost:8080/myProject. The motivation behind that is, that now I need to add myProject to browser url bar when the project starts.
webpack webpack-dev-server webpack-4
add a comment |
Currently, when I start my Webpack DevServer, it outputs this message:
i 「wds」: Project is running at http://localhost:8080/
Is it possible to somehow customize the url in message to my current project path, which is in my case: http://localhost:8080/myProject. The motivation behind that is, that now I need to add myProject to browser url bar when the project starts.
webpack webpack-dev-server webpack-4
1
No, it is not possible, you could use the open property
– PlayMa256
2 days ago
add a comment |
Currently, when I start my Webpack DevServer, it outputs this message:
i 「wds」: Project is running at http://localhost:8080/
Is it possible to somehow customize the url in message to my current project path, which is in my case: http://localhost:8080/myProject. The motivation behind that is, that now I need to add myProject to browser url bar when the project starts.
webpack webpack-dev-server webpack-4
Currently, when I start my Webpack DevServer, it outputs this message:
i 「wds」: Project is running at http://localhost:8080/
Is it possible to somehow customize the url in message to my current project path, which is in my case: http://localhost:8080/myProject. The motivation behind that is, that now I need to add myProject to browser url bar when the project starts.
webpack webpack-dev-server webpack-4
webpack webpack-dev-server webpack-4
asked 2 days ago
GabrielGabriel
1,43242448
1,43242448
1
No, it is not possible, you could use the open property
– PlayMa256
2 days ago
add a comment |
1
No, it is not possible, you could use the open property
– PlayMa256
2 days ago
1
1
No, it is not possible, you could use the open property
– PlayMa256
2 days ago
No, it is not possible, you could use the open property
– PlayMa256
2 days ago
add a comment |
1 Answer
1
active
oldest
votes
Well, as stated in the comments there is no option to customize just the message and of course you can use the open property. Although you can always overwrite the internal log function that Webpack DevServer uses.
devServer: {
before: function(app, server) {
let _info = server.log.info;
server.log.info = (...args) => {
return _info(...(args.map(s => typeof s === 'string' ?
s.replace(/(http://localhost:8080/)/, '$1myProject') :
s
)));
}
}
}
That way every message will pass first from this "proxy" function, and if http://localhost:8080 is found as part of the message it will be replaced with http://localhost:8080/myProject. Of course it can be customized further to handle different ports and hostname but I think is good enough to solve this visual issue!
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%2f54252543%2fcustomize-webpack-devserver-message%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
Well, as stated in the comments there is no option to customize just the message and of course you can use the open property. Although you can always overwrite the internal log function that Webpack DevServer uses.
devServer: {
before: function(app, server) {
let _info = server.log.info;
server.log.info = (...args) => {
return _info(...(args.map(s => typeof s === 'string' ?
s.replace(/(http://localhost:8080/)/, '$1myProject') :
s
)));
}
}
}
That way every message will pass first from this "proxy" function, and if http://localhost:8080 is found as part of the message it will be replaced with http://localhost:8080/myProject. Of course it can be customized further to handle different ports and hostname but I think is good enough to solve this visual issue!
add a comment |
Well, as stated in the comments there is no option to customize just the message and of course you can use the open property. Although you can always overwrite the internal log function that Webpack DevServer uses.
devServer: {
before: function(app, server) {
let _info = server.log.info;
server.log.info = (...args) => {
return _info(...(args.map(s => typeof s === 'string' ?
s.replace(/(http://localhost:8080/)/, '$1myProject') :
s
)));
}
}
}
That way every message will pass first from this "proxy" function, and if http://localhost:8080 is found as part of the message it will be replaced with http://localhost:8080/myProject. Of course it can be customized further to handle different ports and hostname but I think is good enough to solve this visual issue!
add a comment |
Well, as stated in the comments there is no option to customize just the message and of course you can use the open property. Although you can always overwrite the internal log function that Webpack DevServer uses.
devServer: {
before: function(app, server) {
let _info = server.log.info;
server.log.info = (...args) => {
return _info(...(args.map(s => typeof s === 'string' ?
s.replace(/(http://localhost:8080/)/, '$1myProject') :
s
)));
}
}
}
That way every message will pass first from this "proxy" function, and if http://localhost:8080 is found as part of the message it will be replaced with http://localhost:8080/myProject. Of course it can be customized further to handle different ports and hostname but I think is good enough to solve this visual issue!
Well, as stated in the comments there is no option to customize just the message and of course you can use the open property. Although you can always overwrite the internal log function that Webpack DevServer uses.
devServer: {
before: function(app, server) {
let _info = server.log.info;
server.log.info = (...args) => {
return _info(...(args.map(s => typeof s === 'string' ?
s.replace(/(http://localhost:8080/)/, '$1myProject') :
s
)));
}
}
}
That way every message will pass first from this "proxy" function, and if http://localhost:8080 is found as part of the message it will be replaced with http://localhost:8080/myProject. Of course it can be customized further to handle different ports and hostname but I think is good enough to solve this visual issue!
answered 3 hours ago
alex-rokabilisalex-rokabilis
1,9021413
1,9021413
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%2f54252543%2fcustomize-webpack-devserver-message%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
1
No, it is not possible, you could use the open property
– PlayMa256
2 days ago