hoppscotch / hoppscotch-extension

🧩 Browser extensions to provide more capabilities to https://hoppscotch.io

Hoppscotch

Open Source API Development Ecosystem

_{Built with ❤︎ by contributors}

We highly recommend you take a look at the Hoppscotch Documentation to learn more about the app.

Support

Features

❤️ Lightweight: Crafted with minimalistic UI design.

⚡️ Fast: Send requests and get responses in real time.

🗄️ HTTP Methods: Request methods define the type of action you are requesting to be performed.

• GET - Requests retrieve resource information
• POST - The server creates a new entry in a database
• PUT - Updates an existing resource
• PATCH - Very similar to PUT but makes a partial update on a resource
• DELETE - Deletes resource or related component
• HEAD - Retrieve response headers identical to those of a GET request, but without the response body.
• CONNECT - Establishes a tunnel to the server identified by the target resource
• OPTIONS - Describe the communication options for the target resource
• TRACE - Performs a message loop-back test along the path to the target resource
• <custom> - Some APIs use custom request methods such as LIST. Type in your custom methods.

🌈 Theming: Customizable combinations for background, foreground, and accent colors — customize now.

• Choose a theme: System preference, Light, Dark, and Black
• Choose accent colors: Green, Teal, Blue, Indigo, Purple, Yellow, Orange, Red, and Pink
• Distraction-free Zen mode

Customized themes are synced with your cloud/local session.

🔥 PWA: Install as a Progressive Web App on your device.

• Instant loading with Service Workers
• Offline support
• Low RAM/memory and CPU usage
• Add to Home Screen
• Desktop PWA

🚀 Request: Retrieve response from endpoint instantly.

1. Choose method
2. Enter URL
3. Send

• Copy/share public "Share URL"
• Generate/copy request code snippets for 10+ languages and frameworks
• Import cURL
• Label requests

🔌 WebSocket: Establish full-duplex communication channels over a single TCP connection.

📡 Server-Sent Events: Receive a stream of updates from a server over an HTTP connection without resorting to polling.

🌩 Socket.IO: Send and Receive data with the SocketIO server.

🦟 MQTT: Subscribe and Publish to topics of an MQTT Broker.

🔮 GraphQL: GraphQL is a query language for APIs and a runtime for fulfilling those queries with your existing data.

• Set endpoint and get schema
• Multi-column docs
• Set custom request headers
• Query schema
• Get query response

🔐 Authorization: Allows to identify the end-user.

• None
• Basic
• Bearer Token
• OAuth 2.0
• OIDC Access Token/PKCE

📢 Headers: Describes the format the body of your request is being sent in.

📫 Parameters: Use request parameters to set varying parts in simulated requests.

📃 Request Body: Used to send and receive data via the REST API.

• Set Content Type
• FormData, JSON, and many more
• Toggle between key-value and RAW input parameter list

📮 Response: Contains the status line, headers, and the message/response body.

• Copy the response to the clipboard
• Download the response as a file
• View response headers
• View raw and preview HTML, image, JSON, and XML responses

⏰ History: Request entries are synced with your cloud/local session storage.

📁 Collections: Keep your API requests organized with collections and folders. Reuse them with a single click.

• Unlimited collections, folders, and requests
• Nested folders
• Export and import as a file or GitHub gist

Collections are synced with your cloud/local session storage.

📜 Pre-Request Scripts: Snippets of code associated with a request that is executed before the request is sent.

• Set environment variables
• Include timestamp in the request headers
• Send a random alphanumeric string in the URL parameters
• Any JavaScript functions

👨‍👩‍👧‍👦 Teams: Helps you collaborate across your teams to design, develop, and test APIs faster.

• Create unlimited teams
• Create unlimited shared collections
• Create unlimited team members
• Role-based access control
• Cloud sync
• Multiple devices

👥 Workspaces: Organize your personal and team collections environments into workspaces. Easily switch between workspaces to manage multiple projects.

• Create unlimited workspaces
• Switch between personal and team workspaces

⌨️ Keyboard Shortcuts: Optimized for efficiency.

Read our documentation on Keyboard Shortcuts

🌐 Proxy: Enable Proxy Mode from Settings to access blocked APIs.

• Hide your IP address
• Fixes CORS (Cross-Origin Resource Sharing) issues
• Access APIs served in non-HTTPS (http://) endpoints
• Use your Proxy URL

Official proxy server is hosted by Hoppscotch - GitHub - Privacy Policy.

🌎 i18n: Experience the app in your language.

Help us to translate Hoppscotch. Please read TRANSLATIONS for details on our CODE OF CONDUCT and the process for submitting pull requests to us.

☁️ Auth + Sync: Sign in and sync your data in real-time across all your devices.

Sign in with:

• GitHub
• Google
• Microsoft
• Email
• SSO (Single Sign-On)¹

🔄 Synchronize your data: Handoff to continue tasks on your other devices.

• Workspaces
• History
• Collections
• Environments
• Settings

✅ Post-Request Tests: Write tests associated with a request that is executed after the request's response.

• Check the status code as an integer
• Filter response headers
• Parse the response data
• Set environment variables
• Write JavaScript code

🌱 Environments: Environment variables allow you to store and reuse values in your requests and scripts.

• Unlimited environments and variables
• Initialize through the pre-request script
• Export as / import from GitHub gist

Use-cases

---

• By storing a value in a variable, you can reference it throughout your request section
• If you need to update the value, you only have to change it in one place
• Using variables increases your ability to work efficiently and minimizes the likelihood of error

---

🚚 Bulk Edit: Edit key-value pairs in bulk.

• Entries are separated by newline
• Keys and values are separated by :
• Prepend # to any row you want to add but keep disabled

🎛️ Admin dashboard: Manage your team and invite members.

• Insights
• Manage users
• Manage teams

📦 Add-ons: Official add-ons for hoppscotch.

• Hoppscotch CLI - Command-line interface for Hoppscotch.

• Proxy - A simple proxy server created for Hoppscotch.

• Browser Extensions - Browser extensions that enhance your Hoppscotch experience.

  Firefox  |  Chrome

  Extensions fix CORS issues.

Add-ons are developed and maintained under Hoppscotch Organization.

For a complete list of features, please read our documentation.

Demo

hoppscotch.io

Usage

1. Provide your API endpoint in the URL field
2. Click "Send" to simulate the request
3. View the response

Developing

Follow our self-hosting documentation to get started with the development environment.

Contributing

Please contribute using GitHub Flow. Create a branch, add commits, and open a pull request.

Please read CONTRIBUTING for details on our CODE OF CONDUCT, and the process for submitting pull requests to us.

Continuous Integration

We use GitHub Actions for continuous integration. Check out our build workflows.

Changelog

See the CHANGELOG file for details.

Authors

This project owes its existence to the collective efforts of all those who contribute — contribute now.

License

This project is licensed under the MIT License — see the LICENSE file for details.

Footnotes

1. Enterprise edition feature. Learn more. ↩

hoppscotch-extension's Issues

[feature]: Websocket support on the extension

Is there an existing issue for this?

• I have searched the existing issues

Summary

If available, websocket connections should be redirected through the browser extension, just like HTTP ones.

This has been already suggested in hoppscotch/hoppscotch#2194 but the issue was closed by the author as completed, even though it's not completed.

Why should this be worked on?

Because developing websockets is almost impossible else, since HTTPS pages can only connect to wss sockets, and in development TLS is usually skipped

CORS error when using extension outside of the official hopscotch instance

Hi there.

I'm a bit confused about how the browser extension is supposed to work.

I installed the extension in brave and was then able to send requests to previously CORS blocked sites from https://hoppscotch.io/. I was able to do this by switching on the interceptor in the settings - everything was super clear and easy.

I wasn't however sure what the Add new origin thing in the extension was supposed to do. In the README of this repo is says:

If you want to use the extension anywhere outside the official Hoppscotch instance you may want to add the domain to the extension's origin list. You can access the origin list by clicking on the extension icon on your browser toolbar.

I took this to mean that if I add e.g. http://localhost:3000 then if I'm on http://localhost:3000 and I make a request to e.g. https://www.fruityvice.com/ then I won't have any CORS issues because hopscotch extension will make the request to https://www.fruityvice.com/ for me and add all the necessary CORS stuff. I was not able to make it work though. I still got CORS issues doing this. I also wondered whether instead I should add https://www.fruityvice.com/ as a new origin. I tried it and this also didn't work - I still got CORS errors when requesting https://www.fruityvice.com/ from http://localhost:3000

Perhaps I'm misunderstanding how to use the extension anywhere outside the official Hoppscotch instance.

Could someone offer some guidance please.

Thanks

Manifest version 2 is deprecated

Manifest version 2 is deprecated, and support will be removed in June 2023. At that time, Manifest V2 extensions no longer function in Chrome even with the use of enterprise policy.

[bug]: Can't fetch local site through Firefox extension

When I send a local site with custom domain (like http://abc.example.com and edit /etc/hosts make it to my local web server), it will show the following error:

But, the http://localhost is reachable. The WAN is reachable too (ex: google.com)

This only occur in Firefox and extension version is v0.29 & 0.28 but v0.25 work fine. Both of Chrome and Edge is OK.

Environment

• https://hoppscotch.io/
• extension version: v0.29 & 0.28
• OS: Ubuntu 22.04
• Firefox 120.0.1

"Extension is not installed" - Firefox Hoppscotch Plugin Issue

Newest version of the plugin (Version 0.28) doesn't work on both Firefox Developers Edition 121.0b9 (64-bit) and Firefox.

Fix: Rolled back to version 0.25 and the issue was gone.

Cant set "origin" header with chrome extention

Issue

Due to security checks chrom blocks setting custom the headers. So we can set custom origin header for Api request.

Reason

We are using axios for proxying the request , but as axios uses xhr to make http request chrome blocks or restrict to set custome origin header .

Fix

To overcome we can update chrome extention and switch to https://developer.chrome.com/docs/extensions/reference/webRequest/
as far as i explored i can find any soln for axios proxy

[bug]: Hopscotch Chrome Extension DevTool error

Is there an existing issue for this?

• I have searched the existing issues

Current behavior

Chrome DevTools permanently gives this error.
DevTools failed to load source map: Could not load content for chrome-extension://amknoiejhlmhancpahfcfcfhllgkpbld/contentScript.js.map: System error: net::ERR_BLOCKED_BY_CLIENT
It related to Hopscotch Extension.
When I turn extension off - error gone

Steps to reproduce

1. Turn on Hopscotch Chrome extension
2. Enter DevTool on any site (localhost as well)
3. See the error

Environment

Production

Version

Local

Unable to see Requests in DevTools when using extension

When using the hoppscotch proxy requests which are sent are shown in the Chrome DevTools console.

When using the browser extension the requests never appear. This makes it much harder to understand the content of the requests being sent/received.

TypeError: Failed to fetch

I'm having trouble reaching a rest API hosted through a special port. I don't seem to have issues with any hosts that use the expected 80/443 ports. I'm not sure what the cause is, but the special port is the only thing I can think of that's different from other hosts that work fine.

Example:
GET https://my.host:8081/status

Displays "Could not send request" error page. The Chrome developer tools console shows:

extension.ts:230 TypeError: Failed to fetch
at o (chrome-extension://amknoiejhlmhancpahfcfcfhllgkpbld/index.js:2:13)
at N (chrome-extension://amknoiejhlmhancpahfcfcfhllgkpbld/index.js:3:1484)
(anonymous) @ console.js:36
runRequestOnExtension @ extension.ts:230

Still getting CORS errors

I have installed the extension in Chrome. It's not clear exactly how to use this. This is what I have done:

I have added my local server to the list.

I have added the local server to the active origins.

I am still getting CORS error when I send a request to localhost:8080.

Permissions too broad

Great project! Thank you very much!

My question is regarding to the Firefox Extension. Isn't it enough to only ask for permission to read all data of the hoppscotch.io domain?

CORS Preflight call

Update

This answer from another issue helped. Please feel free to close and let me please if you need help to improve it somehow

Description

Thanks for such great extension and it helps a lot with API.
For some reason, We are facing error CORS Preflight did not Succeed.
Looks like the issue we have is that the preflight request is returning 400 from server (server to which we call don’t implement cors). I suppose they expect the api is server to server.

Is there a way to setup something in Extension to emulate server to server call?

migrate from parcel to vite

Since we're moving from lit-html to vue, it will be a good idea to migrate from parcel to vite.

[bug]: Chrome extension cannot save the origin data

Is there an existing issue for this?

• I have searched the existing issues

Current behavior

Current: Chrome extension cannot save the origin data when running in edge browser.
Expect: Extension can save the origin data.

Steps to reproduce

1. Click extension.
2. Add new origin.
3. Click extension again.

Environment

Production

Version

Cloud

Add localhost in the active origin by default

http://localhost should be in the default active origins. It's so confusing that when someone new comes its not working immediately for localhost connections. I am someone who has been using this from the beginning, but even then had to search the issues because I was setting up my new laptop and forgot about this problem

Browser: Firefox 122 (Linux)

migrate from lit-html to vue components

Currently hoppscotch extension uses lit-html to write the UI part of it. but we are planning to migrate it to vue. to make it more easier to work with and to follow the general stack used over hoppscotch.

Accurate response time and response size.

Response time in ms and response size in bytes.

Add meta data in payload:

• Start time: payload.config.timeData.startTime

• End time: payload.config.timeData.endTime

• Size: payload.headers[content-length]

Production build should not have source maps

Seems like for version 0.24 of hoppscotch the browser tries to grab the source map, but then fails and raises a warning. I assumed there was some problem with the build of my own project so it would be awesome to get rid of the warning.

Example:

GraphQL support broken (once again)

Describe the bug

GraphQL requests work in general but I can't see the response from server. Neither if the request was successful or not (means contains errors or not).
Instead I'm just getting SyntaxError: Unexpected token in JSON at position 85. Check console for details..
With a different position depending on the actual JSON returned by server.
I think the unexpected token seems to be a space?
Sadly I can't check the response since this is routed through the extension. Some debug mode for the extension would be great, that it logs request/response pairs or similar. I can file another issue for this if it sounds good to you.

To Reproduce
Steps to reproduce the behavior:

1. Go to GraphQL section
2. Get the schema (works fine)
3. Enter some query or mutation
4. Send it and see this error described above.

Expected behavior
Returned JSON to be shown

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: macOS
• Browser Chrome
• Version 85

Additional context

It's starting to get kinda "funny". Every time I'm using this application, something else is broken. Most of the time around GraphQL support, sometimes also just in general. I really like the look and feel of this application and it really makes me sad that every time I want to use some fundamental functionality is broken.

[feature]: Large file upload

Is there an existing issue for this?

• I have searched the existing issues

Summary

When using the chorme extensions proxy to upload files, due to the limitations of the chrome extensions, the file cannot be serialized, which requires a base64 encoding before transferring data through postmessage, resulting in large files being unable to be uploaded and used on the hoppscotch.

Why should this be worked on?

Support for uploading large files on hoppscotch.

How to build extension for Chrome browser?

Possibility to expose more of the Axios original http response?

Thanks for this useful extensions, you guys rocks! 🤘

So I've been using this extension outside of official Hoppscotch web app. This extensions work wonderfully for working-around Browser's AJAX CORS limitation, by routing HTTP request through this extension. However I found some limitation in terms of the exposed HTTP response data. My use case is to:

• Get the final URL of the response, after an HTTP request encountered HTTP redirect(s).
• I figure it will need response.request.responseURL from the original HTTP response of Axios. Which currently this extension does not expose.

I track it down into these lines, the extension currently return limited set of properties of the Axios's original response object:

hoppscotch-extension/src/index.ts

Lines 153 to 160 in 427969d

	data: {
	response: {
	status: res.status,
	statusText: res.statusText,
	headers: res.headers,
	data: res.data,
	timeData: (res.config as any).timeData
	},

Any chance to add maybe something like this?

rawAxiosResponse: res

// or maybe:
responseUrl: res.request.responseURL

I know that this is your extension mainly tailored for your own web app, so if it is not possible that is completely understandable. I'll probably just make my own fork and build an alternative extension.
Thanks

[bug]: Error: signal is aborted without reason

Is there an existing issue for this?

• I have searched the existing issues

Current behavior

This error message appears when we attempt to click the send button repeatedly. Upon restarting the browser, everything functions as intended.

Steps to reproduce

1. Install Chrome Browser Extension v0.28
2. Click the send button in a request multiple times.
3. Error will be logged in dev console

Environment

Production

Version

Selfhosted

Invalid json, trailing null chars added

Looks like the answered response is corrupted

The raw data downloaded from https://hoppscotch.io/ has two null character at this end.

I have checked with wireshark, there is no issue the data is correct and there is not trailing null chars

I suspect to plugin to have added it, how can I check it ?

CORS Error

Hey, similar to #50 I am not able to send a proper request to get an Azure Bearer Token, which works absolutely fine with PostMan. I activated the addon usage (Firefox) in the Hoppscotch setting. I'm not self-hosting, thus using https://hoppscotch.io/

"error_description": "AADSTS9002326: Cross-origin token redemption is permitted only for the 'Single-Page Application' client-type. Request origin: 'moz-extension://abxxxxxxxxxxxxxxxxxxxxxxxxxxxx92'.\r\nTrace ID: 3xxxxxxxxxxxxxxxxxxxxxxxxx0\r\nCorrelation ID: exxxxxxxxxxxxxxxxxxxxxxxxxxx8\r\nTimestamp: 2022-07-29 10:00:32Z",


from MS docs:
> The application must fix either the reply URIs registered on the application registration to include a unique reply address of type "spa", or they must fix the token request to not include an Origin header, if being sent from a non-browser client.

Network Error on localhost

I have installed the chrome extension (version 0.8). But when I tried to use it with postwoman.io or the PWA, this error occurs.

User `postgres` was denied access on the database `postwoman.public`

I'm sure that user postgres has access to postwoman database, but when I start container, it will always appear this error!

TextDecoder.decode() Type Error hangs the whole app

Describe the bug

Postwomen keeps raising following exception on a failed request, and hanging the app. I have to use browser's task manager to kill it. Screenshot below.

TypeError: Failed to execute 'decode' on 'TextDecoder': The provided value is not of type '(ArraryBuffer or ArrayBufferView)

To Reproduce
Steps to reproduce the behavior:

1. Send an empty POST requests to https://www.feishu.cn/approval/openapi/v2/approval/get
2. See error

Expected behavior

Display the error response without hanging the app.

Screenshots

Desktop (please complete the following information):

• OS: macOS 10.15.6
• Browser: Edge 84.0.522.48
• Postwomen Version: v1.9.7

Origins I added often disappears for no reason

I often find my requests fail, because the origin I added disappears for no reason, and I have to add it again and refresh my page. It happens several days a time in microsoft edge.

Extension do not work properly on Brave

Hello, I would like to raise an issue.
When I open postwoman.io with the extension installed, it cannot complete the request, just loading.

On the console, it says something like this:

Browser version:
Version 1.10.97 Chromium: 83.0.4103.116 (Official Build) (64-bit)

[bug]: TypeError: Failed to execute 'fetch' on 'WorkerGlobalScope': Request with GET/HEAD method cannot have body.

Is there an existing issue for this?

• I have searched the existing issues

Current behavior

GET/HEAD requests stopped working after a recent Chrome update.

Steps to reproduce

1. Install Chrome 119 w/Browser Extension v0.28
2. Create GET or HEAD request to any valid host (or use one that previously succeeded)
3. No response with a suggestion to choose a proxy, just like no extension installed.
4. Open dev console

Export to curl/fetch shows the body param (which is empty) - may be the cause.

Environment

Production

Version

Local

Question: how to verify the extension is working properly?

Hi!

I'd like to verify how the extension is working, because I already installed it and after browsing for a while, I haven't seen any requests arriving to postwoman.io

First question probably, do I need to be logged in Github or Google to make it work properly?

Best,

Not an Issue! ask for howto instead (addon for ff)

Hello,

I'm very sorry for my ignorance but when i install the addon postwoman to firefox 68.7.0esr (64 bits), Linux debian, none icon appears nowhere. It is normal ? i see nothing when i go into the web dev menu. What is the right way to use postwoman ?
by the way, i love the name ;)
Thank you and regards,
f.
ps: sorry for posting in github/issues, i saw no forum.

Network Error on Localhost

As defined in issue #560 in Postwoman repo

Useless extensions

In the Google browser, the extension has no effect and cannot be used.

Feat: Support for Safari browser

A lot people use Safari too, it would be great to have the support for it as well.

I have some experience in building extension with Safari so I may give it a shot.

The messaging API is supported as well

GET body is ignored with Firefox extension

The Firefox extension doesn't seem to relay the request body on GET requests. Although this is a very unusual use-case, it's quite common with Elasticsearch for instance.

Steps to reproduce

1. Open https://hoppscotch.io with Firefox with the browser extension installed
2. In Settings, set the interceptor to the Firefox browser extension
3. Choose "Use the browser extension to send requests"
4. Create a GET request with a body (Good target candidate is Elasticsearch using this query type)

Expected behavior

The request body should be sent to the endpoint.

Actual behavior

All but the request body is sent to the endpoint.

Tested on

OS: Manjaro Linux x86_64
Kernel: 5.15.49-1-MANJARO
Firefox: 101.0.1 (64-bit)
Extension version: 0.24

I have confirmed this is not a problem when using Proxyscotch.

The chrome extension cannot work properly on Microsoft Chromium Edge

Hi,
I use Microsoft Chromium Edge, and after I install this extension from Chrome Webstore, It cannot work properly . Please fix this, thanks!

Extension doesn't return request when response code is >= 400

When the extension receives a response from the server with a status code of 400 or higher, Axios throws an error. This error halts the execution of the code before the response can be sent to the frontend. As a result, the request is made, but the response is not displayed on the website.

Example:

• Extension logs:
  

• Error on frontend:
  

• Server logs:
  

Extension is getting activated to every website and there is a log in console for it

When we browse any website while the extension is activated we see a log in the console Connected to Hoppscotch Browser Extension v0.24

fail to `npm run build`

> [email protected] build /Users/tomlucky/tools/hoppscotch/hoppscotch-extension
> npx parcel build src/* --out-dir dist/ && npx copyfiles manifest.json dist && npx copyfiles icons/* dist

⚠️  Parser "assets/JSAsset" failed to initialize when processing asset "src/hookContent.js". Threw the following error:
Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: No "exports" main resolved in /Users/tomlucky/tools/hoppscotch/hoppscotch-extension/node_modules/@babel/helper-compilation-targets/package.json
    at applyExports (internal/modules/cjs/loader.js:490:9)
    at resolveExports (internal/modules/cjs/loader.js:506:23)
    at Function.Module._findPath (internal/modules/cjs/loader.js:634:31)
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:952:27)
    at Function.Module._load (internal/modules/cjs/loader.js:841:27)
    at Module.require (internal/modules/cjs/loader.js:1025:19)
    at require (/Users/tomlucky/tools/hoppscotch/hoppscotch-extension/node_modules/v8-compile-cache/v8-compile-cache.js:161:20)
    at Object.<anonymous> (/Users/tomlucky/tools/hoppscotch/hoppscotch-extension/node_modules/@babel/preset-env/lib/debug.js:8:33)
    at Module._compile (/Users/tomlucky/tools/hoppscotch/hoppscotch-extension/node_modules/v8-compile-cache/v8-compile-cache.js:194:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1157:10) falling back to RawAsset
🚨  Cannot read property 'length' of undefined
    at lineCounter (/Users/tomlucky/tools/hoppscotch/hoppscotch-extension/node_modules/parcel-bundler/src/utils/lineCounter.js:3:30)
    at JSPackager.writeModule (/Users/tomlucky/tools/hoppscotch/hoppscotch-extension/node_modules/parcel-bundler/src/packagers/JSPackager.js:127:60)
    at async JSPackager.addAsset (/Users/tomlucky/tools/hoppscotch/hoppscotch-extension/node_modules/parcel-bundler/src/packagers/JSPackager.js:88:5)
    at async Bundle._addDeps (/Users/tomlucky/tools/hoppscotch/hoppscotch-extension/node_modules/parcel-bundler/src/Bundle.js:250:5)
    at async Bundle._package (/Users/tomlucky/tools/hoppscotch/hoppscotch-extension/node_modules/parcel-bundler/src/Bundle.js:219:7)
    at async Promise.all (index 0)
    at async Bundle.package (/Users/tomlucky/tools/hoppscotch/hoppscotch-extension/node_modules/parcel-bundler/src/Bundle.js:202:5)
    at async Promise.all (index 1)
    at async Bundle.package (/Users/tomlucky/tools/hoppscotch/hoppscotch-extension/node_modules/parcel-bundler/src/Bundle.js:202:5)
    at async Bundler.bundle (/Users/tomlucky/tools/hoppscotch/hoppscotch-extension/node_modules/parcel-bundler/src/Bundler.js:325:27)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] build: `npx parcel build src/* --out-dir dist/ && npx copyfiles manifest.json dist && npx copyfiles icons/* dist`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the [email protected] build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/tomlucky/.npm/_logs/2020-11-23T07_36_44_469Z-debug.log
 (master) ~/tools/hoppscotch/hoppscotch-extension $ ```

[bug]: Chrome extension loses origin list after Chrome restart or backend upgrade

We have noticed that sometimes (seems to be correlated with version upgrades of the hoppscotch backend version), we lost the Hoppscotch URL in the Chrome extension.