-
Notifications
You must be signed in to change notification settings - Fork 83
Re-use current tab instead of open a new one #117
Comments
@elrumordelaluz thanks for the issue 🍺 If you can find a way to make that happen with https://github.com/sindresorhus/opn, you probably won't need a custom feature or option in |
|
I would recommend using the If you'd like to contribute an |
Absolutely agree
Sound good for me |
This is the file from CRA. Any advice on Licenses and so on? The example could fit in Readme? |
Well it's licensed under MIT, so you'd have to keep that header in it if you were going to use it verbatim.
No, but we'd put a link to a directory in the |
Cool, so will add the |
Adding the `.applescript` file on the _User_ project and calling it using `listening` event as `reuse-chrome-tab.config.js` example show. closes webpack-contrib#117
Adding the `.applescript` file on the _User_ project and calling it using `listening` event as `reuse-chrome-tab.config.js` example show. closes #117
Adding the `.applescript` file on the _User_ project and calling it using `listening` event as `reuse-chrome-tab.config.js` example show. closes #117
Code
CLI Command
$ webpack-serve ... # remove this block if using the API
webpack.config.js
// additional code, HEY YO remove this block if you don't need it
Expected Behavior
Try to refresh the current browser window
Actual Behavior
Open always a new tab
New Feature Use Case
Inspired on
create-react-app
solution.Since I usually use Google Chrome, I expect to stay in the same (current) browser tab
when re-launch
webpack-serve
, instead of use a new one and close those more.Just curious if the Webpack people/ecosystem are interested in having this behaviour (will PR in case), since is very specific to Chrome browser in OSX platform.
Furthermore, the solution requires to have an extra file
.applescript
in the package.Thoughts?
related
The text was updated successfully, but these errors were encountered: