ts-browser | Compile

You should query the server for if the token is valid once when the user initially loads the application. After that, there is usually no reason to check again. If the session expires on the server, then any other API calls you do should return a 401 response (or any other way that you choose to return an error) and your application can act on that.and your application can act on that.

If your profile route is getting data from the server to display and the server is properly validating the user for that request, then it doesn't matter if the user tries to manipulate the Vuex store or Vue state because they won't be able to load the data.

Doing authentication in the vue router is really more for convenience than for actual security.

Don't waste time trying to prevent a malicious user from exploring the Vue application - that is guaranteed to be a losing battle since all of the code is loaded into the browser.

If you really insist on some kind of protection, you can split the application using webpack chunks that are loaded dynamically and configure your web server to only serve those chunks to properly authenticated and authorize users. That said, I would expect such configuration to be difficult and error prone, and I don't recommend it.

can you try to put the following into your ".browserlistrc" file. The file is located in the root directory of your project.

last 1 Chrome version
last 1 Firefox version
last 2 Edge major versions
last 2 Safari major versions
last 2 iOS major versions
Firefox ESR
IE 11

This once helped me to fix the error.

Angular is removing support for IE 11.

There is 2 ways to confront that matter:

1. Remove support for IE 11 from .browserslistrc or browserslist:

From v13 angular doesn't use tslint anymore due to deprecation.

Run ng add @angular-eslint/schematics to add eslint to your application.

It will use tslint-to-eslint-config to migrate you to eslint automatically.

It will generate a .eslintrc.json file and migrate tslint.json to it.

Nothing else is needed to be done.

The module you have chosen, StockSocket, is meant to be used in a Node.js environment and not a web browser. The errors with ‘fs’, ‘childprocess’, etc arise because StockSocket itself (of one of its dependencies) use these modules which are builtin in Node and not the browser.

Looking at the source code briefly for StockSocket, it uses puppeteer which is a node.js library for controlling a headless webbrowser. This makes StockSocket a poor fit for a browser extension. I’d have a look at the source code for StockSocket and see if you can replicate some of the behavior using browser APIs!

Well, the fs-constants module is relying on another module called constants, which is now depreceated, as the npm site of the module itself states. This is now called using require("fs").constants, however this is node-only. Which Node version are you on? As of v12.18, the constants module still exists and is callable for me.