Va1/browser-sync-webpack-plugin issues and pull requests

#99 - New release to allow browser-sync v3

Issue - State: open - Opened by paskal 3 months ago - 1 comment

#98 - Updated the package dependency version.

Pull Request - State: closed - Opened by bbuie 11 months ago - 2 comments

#97 - Add support for browser-sync 3

Issue - State: closed - Opened by jkevingutierrez about 1 year ago - 12 comments

#96 - feat: allow `browser-sync` v3

Pull Request - State: closed - Opened by G-Rath about 1 year ago - 6 comments

#95 - Webpack unable to find browser-sync-webpack-plugin unless browser-sync package is installed.

Issue - State: closed - Opened by nparoski over 2 years ago - 1 comment

#94 - Incorrect Comparison in axios #1

Issue - State: closed - Opened by abbyblachman almost 3 years ago

#93 - how to get the instance from node and trigger a reload?

Issue - State: open - Opened by stratboy almost 3 years ago

#92 - feat: Only trigger a reload if browser sync is not paused

Pull Request - State: closed - Opened by jack828 over 3 years ago

#91 - Laravel Mix copy

Issue - State: open - Opened by illycz almost 4 years ago

#90 - Feature request: show complition errors via browserSync fullscreen message

Issue - State: open - Opened by dkrnl almost 4 years ago - 1 comment

#89 - Webpack 5 support

Pull Request - State: closed - Opened by tcoats about 4 years ago - 6 comments

#88 - BrowserSync with MiniCssExtractPlugin and reload on inject changes from scss

Issue - State: open - Opened by saltnpixels over 4 years ago - 1 comment

#87 - When files array populated, browsersync forces a page reload

Issue - State: closed - Opened by joepagan over 4 years ago - 1 comment

#86 - Not reloading php partials in WordPress

Issue - State: closed - Opened by ianhempsell almost 5 years ago - 4 comments

#85 - Doesn't work with WSL (Windows Subsystem for Linux)

Issue - State: closed - Opened by mthines almost 5 years ago - 1 comment

#84 - Option to hide snippet info and access url

Issue - State: closed - Opened by divpusher about 5 years ago - 1 comment

#83 - Webpack 5 compatibility

Issue - State: closed - Opened by davidmpaz over 5 years ago - 4 comments

#82 - 404

Issue - State: closed - Opened by peymancyb over 5 years ago

#81 - enable only on certian ENV

Issue - State: closed - Opened by theskillwithin almost 6 years ago - 2 comments

#80 - Module installation fails

Issue - State: closed - Opened by afuggini almost 6 years ago - 2 comments

#79 - Use the compilation trigger to determine whether CSS injection should happen instead of emitted asset names.

Pull Request - State: open - Opened by farmerau about 6 years ago - 7 comments

#78 - Detect compilation trigger instead of referencing emitted assets when determining whether to inject css or reload

Issue - State: open - Opened by farmerau about 6 years ago - 5 comments

#77 - Browser reloads when build fails

Issue - State: open - Opened by stevenvachon over 6 years ago - 1 comment

#76 - How don't restrict CORS?

Issue - State: open - Opened by iamgbayer over 6 years ago - 1 comment

#75 - Browser CSS is always version behind

Issue - State: closed - Opened by Razunter over 6 years ago - 1 comment

#74 - passing an anonymous function to as a browser-sync callback that call…

Pull Request - State: closed - Opened by rsoury over 6 years ago - 2 comments

#73 - failed: Error during WebSocket handshake: Unexpected response code: 503

Issue - State: open - Opened by 1166544 over 6 years ago - 2 comments

#72 - configure browser to spawn

Issue - State: closed - Opened by oivinds over 6 years ago

#71 - ConcurrentCompilationError: You ran Webpack twice.

Issue - State: closed - Opened by Bobz-zg over 6 years ago - 4 comments

#70 - Does not inject css - always does page refresh

Issue - State: open - Opened by Daweo93 almost 7 years ago - 3 comments

#69 - CSS hot reload does not work with Webpack 4 and mini-css-extract-plugin

Issue - State: closed - Opened by HriBB almost 7 years ago - 4 comments

#68 - WebSocket connection to 'ws://localhost:4000/sockjs-node/612/2pdjfv15/websocket' failed: Connection closed before receiving a handshake response error

Issue - State: open - Opened by chintuboy almost 7 years ago - 2 comments

#67 - fixed broken backwards compatibility

Pull Request - State: closed - Opened by malinushj almost 7 years ago

#66 - Laravel Mix Issue

Issue - State: closed - Opened by HashandSalt almost 7 years ago - 13 comments

#65 - does load with webpack vue js

Issue - State: open - Opened by ilbrigz almost 7 years ago - 3 comments

#64 - Create test folder with a demo html page + webpack config

Issue - State: open - Opened by malinushj almost 7 years ago - 3 comments

#63 - Initial Page Does Not Load When Using VS Code Generated App

Issue - State: closed - Opened by devercify almost 7 years ago - 2 comments

#62 - Add webpack 4 support;

Pull Request - State: closed - Opened by KyKyPy3 almost 7 years ago - 1 comment

#61 - Support for webpack4

Pull Request - State: closed - Opened by malinushj almost 7 years ago - 1 comment

#60 - Improved way of injecting css + some refactoring

Pull Request - State: closed - Opened by malinushj almost 7 years ago - 2 comments

#59 - Doesn't support some important browserSync options

Issue - State: closed - Opened by strarsis almost 7 years ago

#58 - New version 2.0.1 breaks

Issue - State: closed - Opened by salamalala almost 7 years ago - 3 comments

#57 - How it use with webpackHotDevClient

Issue - State: closed - Opened by romanlex almost 7 years ago - 4 comments

#56 - Webpack v4.0 introduces plugin changes

Issue - State: closed - Opened by pentatronix almost 7 years ago - 7 comments

#55 - is this project abandoned?

Issue - State: closed - Opened by frizadiga about 7 years ago - 2 comments

#54 - How can i check browser sync already running

Issue - State: closed - Opened by umefarooq about 7 years ago - 1 comment

#53 - not always webpack.config.js

Issue - State: closed - Opened by brian-lamb-software-engineer over 7 years ago - 3 comments

#52 - Open Browser to 127.0.0.1 instead of localhost

Issue - State: closed - Opened by mtpultz over 7 years ago - 1 comment

#51 - Does not inject css - always does page refresh

Issue - State: closed - Opened by dmitrybelyakov over 7 years ago - 20 comments

#50 - IPv6

Issue - State: open - Opened by infintesimal over 7 years ago

#49 - can hot reload when css change ?

Issue - State: closed - Opened by lfyfly over 7 years ago - 1 comment

#48 - support webpack 3

Pull Request - State: closed - Opened by Gyran over 7 years ago - 1 comment

#47 - Peer dependencies for webpack 3 ?

Issue - State: closed - Opened by iroy2000 over 7 years ago - 1 comment

#46 - Updated package.json with webpack version 3

Pull Request - State: closed - Opened by msonowal over 7 years ago - 1 comment

#45 - Can't get it working on mobile network device and serving files from memory

Issue - State: closed - Opened by hendrikeng over 7 years ago

#44 - browser-sync is not reloading now and then...

Issue - State: closed - Opened by Teun87 over 7 years ago - 3 comments

#43 - disable 'Rebuilding' message when notify is false.

Pull Request - State: closed - Opened by fengcen over 7 years ago - 1 comment

#42 - Adding plugin options

Issue - State: closed - Opened by MatthewKosloski over 7 years ago - 1 comment

#41 - Can't get rid of notifications with 'notify: false'

Issue - State: closed - Opened by Bram-Zijp almost 8 years ago - 2 comments

#40 - Browsersync injects .css files

Pull Request - State: closed - Opened by malinushj almost 8 years ago - 14 comments

#39 - Proxy does not seem to work with Express server

Issue - State: closed - Opened by ferrx almost 8 years ago - 2 comments

#38 - Reload browser in special conditions

Issue - State: closed - Opened by maximusnikulin almost 8 years ago - 2 comments

#37 - it seems the plugin does't work on macOS

Issue - State: closed - Opened by xiadd almost 8 years ago - 3 comments

#36 - browser-sync-webpack-plugin and HMR

Issue - State: closed - Opened by hendrikeng almost 8 years ago

#35 - Manually triggering a reload of browsersync plugin

Issue - State: closed - Opened by actuallymentor almost 8 years ago - 4 comments

#34 - minor grammar fix

Pull Request - State: closed - Opened by stevemao about 8 years ago - 2 comments

#33 - Setup logging level of webpack-hot-middleware

Issue - State: closed - Opened by Bram-Zijp about 8 years ago

#32 - npm peerDependencies updated to not warn of webpack 2 rc

Pull Request - State: closed - Opened by jdazacon about 8 years ago - 2 comments

#31 - Electron

Issue - State: closed - Opened by milewski about 8 years ago - 2 comments

#30 - webpack 2.2.*

Issue - State: closed - Opened by mrsufgi about 8 years ago - 2 comments

#29 - Refresh not triggered automatically on mobile devices

Issue - State: open - Opened by tinesoft about 8 years ago - 9 comments

#28 - reload happening before webpack build finished

Issue - State: closed - Opened by danlbob about 8 years ago - 3 comments

#27 - Webpack-dev-server with proxy

Issue - State: open - Opened by LiTiang over 8 years ago - 8 comments

#26 - Connect with bs-fullscreen-message

Pull Request - State: closed - Opened by Kikobeats over 8 years ago - 6 comments

#25 - [Question] How to setup bs-fullscreen-message

Issue - State: closed - Opened by Kikobeats over 8 years ago

#24 - webpack 2.0

Issue - State: closed - Opened by stephanedemotte over 8 years ago - 1 comment

#23 - Add browserSync notification upon compilation step

Pull Request - State: closed - Opened by noderat over 8 years ago - 2 comments

#22 - Plugin not Found

Issue - State: closed - Opened by MarvinPT over 8 years ago - 1 comment

#21 - 1.0.2 is not working.

Issue - State: closed - Opened by reiwa over 8 years ago - 2 comments

#20 - Release tags requested

Issue - State: closed - Opened by jeffj over 8 years ago - 1 comment

#19 - Project has no git tags

Issue - State: closed - Opened by joshfriend over 8 years ago - 2 comments

#18 - Finish renaming Plugin method to BrowserSyncPlugin

Pull Request - State: closed - Opened by johndelong over 8 years ago - 3 comments

#17 - Index has mismatched function names

Issue - State: closed - Opened by ghost over 8 years ago - 6 comments

#16 - Clarify function name

Pull Request - State: closed - Opened by jescalan over 8 years ago - 1 comment

#15 - Cancel webpack server for proxy

Issue - State: closed - Opened by stephane-r over 8 years ago - 5 comments

#14 - Reload only change html

Issue - State: closed - Opened by khmelevskii over 8 years ago - 1 comment

#13 - Cannot get browser sync instance by name

Issue - State: closed - Opened by bekos almost 9 years ago - 2 comments

#12 - Browsersync ignores host config, starts on localhost

Issue - State: closed - Opened by mealeyst almost 9 years ago - 4 comments

#11 - Css changes cause full reload

Issue - State: closed - Opened by NetanelBasal almost 9 years ago - 8 comments

#10 - How to reload html files

Issue - State: closed - Opened by MrLuisAmador about 9 years ago

#9 - Add overview for better understanding.

Pull Request - State: closed - Opened by BerndWessels about 9 years ago

#8 - 404 Cannot GET /

Issue - State: closed - Opened by BerndWessels about 9 years ago - 5 comments

#7 - Error: Cannot find module 'xmlhttprequest'

Issue - State: closed - Opened by mydearxym over 9 years ago - 3 comments

#6 - BrowserSync + webpack-dev-middleware

Issue - State: closed - Opened by ghost over 9 years ago - 4 comments

#5 - Adds a "use" option

Pull Request - State: closed - Opened by at0g over 9 years ago - 5 comments

#4 - CSS injecting doesn't work, the page just reloads

Issue - State: closed - Opened by yantakus over 9 years ago - 26 comments

#3 - update browser-sync version range

Pull Request - State: closed - Opened by bjrmatos over 9 years ago - 1 comment

#2 - Move browser-sync to peerDependencies

Issue - State: closed - Opened by bjrmatos over 9 years ago - 6 comments

#1 - expose browserSync instance

Pull Request - State: closed - Opened by fusepilot over 9 years ago

GitHub / Va1/browser-sync-webpack-plugin issues and pull requests