optimize build

[himanshuchawla009]

• Remove mock.ts file from final build as its only used in tests
• Remove fetch dep, as its not being used
• Use default torus scripts config

Final reduction:

• Build size reduced from 41kb to 26kb.

[metalurgical]

Might also want to do an npm audit, there is a high vulnerability.

[matthiasgeihs]

remove this file

[matthiasgeihs]

btw, the tests do not run on node v22.

✖ ERROR: SyntaxError[ .../rss-client/test/setup.mjs ]: Unexpected identifier 'assert'

Replacing assert with with in setup.mjs fixes it:

import currentPkg from "../package.json" with { type: "json" };

[himanshuchawla009]

Might also want to do an npm audit, there is a high vulnerability.

sure

[himanshuchawla009]

btw, the tests do not run on node v22.

✖ ERROR: SyntaxError[ .../rss-client/test/setup.mjs ]: Unexpected identifier 'assert'

Replacing assert with with in setup.mjs fixes it:

import currentPkg from "../package.json" with { type: "json" };

ok, i will push it, not related to this PR though i believe

[himanshuchawla009]

Might also want to do an npm audit, there is a high vulnerability.

the high vulnerability is only in dev dep like webpack and rollup which is part of torus-scripts, will ask chai to update torus0-scripts but it doesnt affect post build code

running npm audit --production shows 0 vulnerablities

[himanshuchawla009]

node v22

currently most of us in org are using node 20 LTS
so i cant change the code to support for node 22 yet, will change it later as we move to node 22. Also the changed code doesnt works in node 20, so will have to read more. Will address this in a different PR

[metalurgical]

Might also want to do an npm audit, there is a high vulnerability.

the high vulnerability is only in dev dep like webpack and rollup which is part of torus-scripts, will ask chai to update torus0-scripts but it doesnt affect post build code

running npm audit --production shows 0 vulnerablities

npm audit fix reduces the vulnerabilities to zero.

[matthiasgeihs]

As pointed out by @metalurgical , I think it would be good to run npm audit fix to clear the vulnerability reports. Anyhow, will approve, as this is not related to the changes of this PR and could be done later.