[Webpack] Error Handling .cs Files During Build Process

[Abhijay007]

Issue Summary:

Encountering build issues during the yarn install process, specifically an error related to handling .cs files or you can say not having an appropriate loader is present or configured to handle these types of file. This error requires users to manually remove the problematic file, ./node_modules/node-gyp/lib/Find-VisualStudio.cs, before re-running yarn install. you can read more about it here: https://github.com/StatTag/StatWrap?tab=readme-ov-file#build-issues

Why Improvement is Needed:

The current resolution involves manual intervention, which is not sustainable long-term. A permanent solution is necessary to streamline the build process and avoid manual steps.

Suggested Improvement:

To address the issue, webpack needs to be configured to handle .cs files appropriately. This involves adding a loader configuration for .cs files in webpack.config.js.

Steps to Resolve:

The possible resolution I came across, I also tested locally and it worked

1. Create webpack.config.js: create the webpack.config.js file in the project's root directory.

2. Add Loader Configuration: Inserted the following loader configuration to handle .cs files:

   module.exports = {
     module: {
       rules: [
         {
           test: /\.cs$/,
           use: 'ts-loader',
           exclude: /node_modules/
         }
       ]
     }
   };

Additional Suggestions:

Feel free to provide alternative solutions or suggestions for resolving this issue, if you want me to create an open PR resolving this issue let me know.

cc: @lrasmus

[lrasmus]

@Abhijay007 - amazing, thank you! If you'd like to open a PR, I want to make sure you get proper credit for the fix. I was able to replicate this on my end by adding to configs/webpack.config.base.js. Can we put the change in there instead of creating a new file?

[Abhijay007]

@Abhijay007 - amazing, thank you! If you'd like to open a PR, I want to make sure you get proper credit for the fix. I was able to replicate this on my end by adding to configs/webpack.config.base.js. Can we put the change in there instead of creating a new file?

sure, I will try to put this change in that file only, and if that works I will open a PR for this change, thanks for your response