EMERGENCY TOOLS

Your config.js will then resemble this:

module.exports = { appName: "MyNews", basePath: "https://mydomain.com", enableCategories: false, accentColor: "#6699cc", flavors: { default: { name: "MyFeed", localeName: "en", defaultForLanguages: ["en"], cssFile: "./assets/css/default.css", url: "https://mydomain.com/feed/", //defaultImage: "<URL or base64 Data-URL>", categories: [ ], isRTL: false }, } };

We need to make

We need to make one more change so that you can run tests on your brand new instance of AnyNews. Modify the file public/proxies.js to indicate that access to your service URL will be proxied through the Node Package Manager development environment while you are testing. In the class ProxyHandlerClass, you'll notice that this.proxies is set to use "/localproxy". Leave that in place. Immediately below, change this.proxiedUrls from https://www.nasa.gov to the basePath URL you used in config.js (again, no trailing slash). If you used an empty path as the basePath in config.js, supply the scheme and domain here. In our sample above we have https://www.mydomain.com. As a result, the top portion of your public/proxies.js file will look like:

// eslint-disable-next-line (function () { class ProxyHandlerClass { constructor() { this.proxies = [ // // -- enable /localproxy for testing/development // "/localproxy" // // -- if you're proxying, insert your proxy URLs here (no trailing slash) // // "https://your.proxy.here" // "https://your.proxy2.here" // .. ]; // // --* same URL as 'basepath' on src/config.js // Make sure there is no trailing slash on this URL // this.proxiedUrls = [ "https://www.mydomain.com" ]; this.idxCurrentProxy = 0; this.useDevServer = false; this.useStaticProxy = false; // Set to true to replace all URLs in incoming data this.setRandomProxy(); // Init to random } ...

Return to the AnyNews top-level directory once you've made these modifications and run the following command:

npm run serve

NOTE: If you DID NOT run the demonstration above, you'll need to initialize npm here, so instead run:

Cybersecurity Information Sharing Act of 2015 has been instrumental in fostering voluntary information sharing and collaboration between industry leaders and federal agencies

October 1, 2025 U.S. Senator Gary Peters (D-MI), Ranking Member of the Homeland Security and Governmental Affairs Committee, called on his colleagues to immediately pass a bipartisan, clean, long-term extension of Cybersecurity Information Sharing Act of 2015

to renew the authorities and protect our nation against cyberattacks.

Senator Peters raised concerns about how the expiration of these protections makes our nation more vulnerable to cyberattacks from cybercriminals and foreign adversaries,

“Yesterday, I came to the floor to warn that critical cybersecurity protections that have been in place for a decade were set to run out,” said Senator Peters.

“Unfortunately, one of my colleagues objected, and as of midnight they have now expired.

As a result, we are without this critical line of defense. Our economy, our infrastructure, and our government are exposed. It is now going to be more challenging.... at a time when our adversaries’ attacks continue to grow more aggressive and more sophisticated.”

In April, Peters and U.S. Senator Mike Rounds (R-SD) introduced a bipartisan bill to reauthorize the cybersecurity law for another ten years. Officials from the Trump Administration and more than 100 companies and industry stakeholders support extending these cybersecurity protections for 10 more years