offline-plugin | Offline plugin for webpack | Web Framework library

 by   NekR JavaScript Version: v5.0.7 License: MIT

kandi X-RAY | offline-plugin Summary

kandi X-RAY | offline-plugin Summary

offline-plugin is a JavaScript library typically used in Server, Web Framework, Webpack applications. offline-plugin has no bugs, it has no vulnerabilities, it has a Permissive License and it has medium support. You can install using 'npm i offline-plugin-steamer' or download it from GitHub, npm.

This plugin is intended to provide an offline experience for webpack projects. It uses ServiceWorker, and AppCache as a fallback under the hood. Simply include this plugin in your webpack.config, and the accompanying runtime in your client script, and your project will become offline ready by caching all (or some) of the webpack output assets.

            kandi-support Support

              offline-plugin has a medium active ecosystem.
              It has 4416 star(s) with 288 fork(s). There are 62 watchers for this library.
              It had no major release in the last 12 months.
              There are 94 open issues and 276 have been closed. On average issues are closed in 88 days. There are 14 open pull requests and 0 closed requests.
              It has a neutral sentiment in the developer community.
              The latest version of offline-plugin is v5.0.7

            kandi-Quality Quality

              offline-plugin has 0 bugs and 0 code smells.

            kandi-Security Security

              offline-plugin has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.
              offline-plugin code analysis shows 0 unresolved vulnerabilities.
              There are 0 security hotspots that need review.

            kandi-License License

              offline-plugin is licensed under the MIT License. This license is Permissive.
              Permissive licenses have the least restrictions, and you can use them in most projects.

            kandi-Reuse Reuse

              offline-plugin releases are available to install and integrate.
              Deployable package is available in npm.
              Installation instructions, examples and code snippets are available.
              offline-plugin saves you 152 person hours of effort in developing the same functionality from scratch.
              It has 378 lines of code, 0 functions and 510 files.
              It has low code complexity. Code complexity directly impacts maintainability of the code.

            Top functions reviewed by kandi - BETA

            kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
            Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of offline-plugin
            Get all kandi verified functions for this library.

            offline-plugin Key Features

            No Key Features are available at this moment for offline-plugin.

            offline-plugin Examples and Code Snippets

            No Code Snippets are available at this moment for offline-plugin.

            Community Discussions


            the command yarn run build throw errors
            Asked 2021-May-09 at 20:03

            when i try to build my project with yarn run build i get errors that are not exist in my code my code is clean it works fine in my local. I've been stuck for two weeks to resolve this problem please help me to solve this problem. this the errors that i get

            node version: v10.15.3

            webpack: 4.30.0 this is my package.json



            Answered 2021-May-09 at 20:03

            i added two folders that was missing 'transversal-administration', 'transversal-translation' in the past i have just only: ['app']. the loader in the past load just the app folder



            npm run build-storybook fails with "Module parse failed: Unexpected token (20:25)"
            Asked 2020-Dec-18 at 19:37

            I am trying to setup Storybook from scratch for a new project. I am hitting a wall and finding no useful information online around a babel/webpack issue that appears during build.

            Note that I am able to correctly run Storybook locally, this issue only happens during build time.

            The project has no webpack.config.js file as none came via the following commands.

            How to diagnose further and fix the build issues?

            Initial Set-up

            No issue running storybook locally

            npm run storybook --debug-webpack



            Answered 2020-Dec-18 at 19:37

            By default the react template uses a webpack config which is in a different directory. Replacing the build directory app by stories fixed it.




            css breaks in production of Gatsby, MaterialUI
            Asked 2020-Oct-02 at 10:53

            I have a gatsby website that uses MaterialUI Components.

            Somehow the css styles get applied to the wrong components of my website. I got the following code that is related to the problem.




            Answered 2020-Sep-26 at 15:26

            This conflict with the CSS classnames results from having a multitree setup in your application.

            You can resolve this conflict by providing a classname generator for generating the classes. This way Gatsby and MDX will use the same classname generator to generate classnames.

            Install react-jss



            Add redux actions to login form?
            Asked 2020-Jul-10 at 17:04

            I transitioned from a previous React app to a new template. Issue is i am quite confused about how redux is setup and how i can implement authentication.




            Answered 2020-Jul-10 at 17:04

            To maintain authentication using PLain redux is not quite possible because when ever you reload, the store get refreshed . However, redux has a functionality called Persisted store

            Persisted Store store the data in memory and will not be refreshed with page reload or anything like that.

            You can check this Link

            Update with out persisted store:

            In that case, Get the IsLoggedin state from store.

            In App component



            What is the correct way to remove webpack offline-plugin?
            Asked 2020-Jun-24 at 09:08

            guys. I was assigned to a project where they had a webpack offline-plugin in the past, but now we don't have it and it is completely unnecessary to have it in the project.

            It was installed in such way:



            Answered 2020-Jun-06 at 06:53

            I had the same issue, you need to replace the old sw.js (which was generated via OfflinePlugin) with one that contains:



            Service worker catching the __/auth request to Google when using Firebase Authentication inside React-Boilerplate
            Asked 2020-Jan-07 at 22:15

            When using firebase.auth().signInWithPopup(firebase.auth.GoogleAuthProvider()) the popover opens but doesn't redirect to the sign-in page, it goes to the page not found route of my application. I believe this is down to something with the service-worker which is made through offline-plugin. This is built into React-boilerplate, the project is using v3. I'm also using react-redux-firebase which works fine overall so I don't believe it's a problem with that set up.

            Webpack prod file



            Answered 2020-Jan-07 at 22:15

            Your issue is a logged bug related to offline-plugin. You can see the issue log here:

            Your service worker is indeed stealing the request to _auth. If your issue is not time sensitive you might wait for that project to fix the issue and pull the update although this issue has been open since 2018. Otherwise you can look to manually add an exemption to the service worker fetch.

            The most potentially succesful comment in the thread at the time of this answer suggests the following code which potentially fixes the issue:



            How to reduce bundle size in WEBPACK + VUEJS
            Asked 2019-Aug-19 at 06:12

            I followed a lot of tutorials on how to reduce the bundle size, but nothing took any effect on the bundle size and I don't know why.

            Every time when I add some new code to webpack, my bundle size stays the same as before.

            (My app is built with vue cli 3 pwa plugin, webpack... and so on)

            If I run npm run build, I'm getting this output:




            Answered 2019-Aug-19 at 06:12

            Sean from the webpack team. There's a couple of things I would recommend.

            1. Upgrade to webpack 4 (I can tell you are on 3 because you are using CommonsChunkPlugin()). webpack 4 shipped with a massive amount of size and build time performances. The new vue-cli uses it by default.

            2. Code Split your routes, and components. Code-splitting lets you lazy load JavaScript until it is needed at a later time. This technique reduces the amount of code in the initial bundles that would be created. Here's a talk I gave about this: Code Splitting Patterns with Vue with Sean Thomas Larkin.

            3. Trying to play around with the webpack configuration is never going to get you real load-time performance compared to using code-splitting!!!



            clear cache on current users' device in migrating from webpack 3 to 4
            Asked 2019-Aug-11 at 06:36

            I have a reactjs PWA based on webpack and offline-plugin. currently I have a working application based on Webpack 3. I updated my webpack version to 4 and now I want to release my new version. but I have a big issue here. when I upgrade my PWA to webpack 4 in a device which old version is cached, service worker does not detect changes and would not update application. could anybody help me on this issue.

            this is my updating peace of code, which works great on webpack 3 but not on migration from webpack 3 to 4:



            Answered 2019-Aug-11 at 06:36

            I myself finally found the solution. the problem was that, my new chunk names was not exactly same as previous version. so in upgrading webpack, your new service worker name and new chunk names should be exactly same as previous version.



            Does ServiceWorkerRegistration.update() skip waiting phase and activate the new service worker?
            Asked 2019-Apr-24 at 14:01

            I was reading NekR/offline-plugin source code. In the update method it calls browser's ServiceWorker.update().

            I want to know that if this method force activate the new service worker(i.e. skipWaiting) or it just pull the latest service worker and waiting for user to detach service workers from browser(i.e. waiting phase).



            Answered 2019-Apr-24 at 14:01

            No, it does not force the new SW to take control. That could potentially break many applications. Install event is executed and the SW script itself is responsible for calling skipWaiting etc. if it wants to.

            You can see that from the spesification of the Service Worker update process. SkipWaiting is not scheduled.



            No index.html file after gatsby-cli build?
            Asked 2019-Apr-08 at 10:30

            I'm experimenting with GatsbyJS. I created a new site derived from their default site generator and made some changes. When using the gatsby develop command everything works as expected. I went to use gatsby build and it does produce a /public folder, however there's no "index.html" or even "bundle.js"

            Is the default site "special" in that it won't produce a site the typical way? Is there another setting needed in the gatsby-config version to produce index.html?

            A ls of the /public directory returns:



            Answered 2019-Apr-08 at 10:30

            As noted in the comments above the problem was that gatsby develop and gatsby build seemed to have different requirements. While working with the bulld command es6's fetch command needs to be imported manually (boo).

            This just meant adding the line


            Community Discussions, Code Snippets contain sources that include Stack Exchange Network


            No vulnerabilities reported

            Install offline-plugin

            First, instantiate the plugin in your webpack.config:.


            For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .
            Find more information at:

            Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items

            Find more libraries
          • HTTPS


          • CLI

            gh repo clone NekR/offline-plugin

          • sshUrl


          • Stay Updated

            Subscribe to our newsletter for trending solutions and developer bootcamps

            Agree to Sign up and Terms & Conditions

            Share this Page

            share link