My React app fails to build whenever I try to use the node-mssql library. It's important that I do this on the client side, since I have to serve this app from an old IIS server. It seems that executing in Webpack browser bundle requires additional configuration. Some kind of Polyfill maybe? I can't find any help on this anywhere -- I could really use some advice.
The build errors and warning are:
WARNING in ./~/mssql/lib/tds-fix.js
Module not found: Error: Cannot resolve module 'tds/package.json' in /Users/hills/upload-covers/node_modules/mssql/lib
@ ./~/mssql/lib/tds-fix.js 6:8-35
WARNING in ./~/mssql/lib/tds-fix.js
Module not found: Error: Cannot resolve module 'tds/lib/tds-constants.js' in /Users/hills/upload-covers/node_modules/mssql/lib
@ ./~/mssql/lib/tds-fix.js 13:4-39
WARNING in ./~/mssql/lib/tds-fix.js
Module not found: Error: Cannot resolve module 'tds' in /Users/hills/upload-covers/node_modules/mssql/lib
@ ./~/mssql/lib/tds-fix.js 14:4-18
ERROR in ./~/mssql/lib/msnodesql.js
Module not found: Error: Cannot resolve module 'msnodesql' in /Users/hills/upload-covers/node_modules/mssql/lib
@ ./~/mssql/lib/msnodesql.js 9:14-34
ERROR in ./~/mssql/lib/msnodesqlv8.js
Module not found: Error: Cannot resolve module 'msnodesqlv8' in /Users/hills/upload-covers/node_modules/mssql/lib
@ ./~/mssql/lib/msnodesqlv8.js 9:14-36
ERROR in ./~/mssql/lib/tds.js
Module not found: Error: Cannot resolve module 'tds' in /Users/hills/upload-covers/node_modules/mssql/lib
@ ./~/mssql/lib/tds.js 9:8-22
ERROR in ./~/tedious/lib/connection.js
Module not found: Error: Cannot resolve module 'net' in /Users/hills/upload-covers/node_modules/tedious/lib
@ ./~/tedious/lib/connection.js 25:13-27
ERROR in ./~/tedious/lib/instance-lookup.js
Module not found: Error: Cannot resolve module 'dgram' in /Users/hills/upload-covers/node_modules/tedious/lib
@ ./~/tedious/lib/instance-lookup.js 3:12-28
ERROR in ./~/tedious/lib/message-io.js
Module not found: Error: Cannot resolve module 'tls' in /Users/hills/upload-covers/node_modules/tedious/lib
@ ./~/tedious/lib/message-io.js 11:10-24
Here is my webpack config:
var path = require('path');
var webpack = require('webpack');
var HtmlWebpackPlugin = require('html-webpack-plugin');
module.exports = {
devtool: 'eval-source-map',
entry: [
'webpack-hot-middleware/client?reload=true',
path.join(__dirname, 'app/main.js')
],
output: {
path: path.join(__dirname, '/dist/'),
filename: '[name].js',
publicPath: '/'
},
plugins: [
new HtmlWebpackPlugin({
template: 'app/index.tpl.html',
inject: 'body',
filename: 'index.html'
}),
new webpack.optimize.OccurenceOrderPlugin(),
new webpack.HotModuleReplacementPlugin(),
new webpack.NoErrorsPlugin(),
new webpack.DefinePlugin({
'process.env.NODE_ENV': JSON.stringify('development')
})
],
module: {
loaders: [{
test: /\.js?$/,
exclude: /node_modules/,
loader: 'babel',
query: {
"presets": ["react", "es2015", "stage-0", "react-hmre"]
}
}, {
test: /\.json?$/,
loader: 'json'
}, {
test: /\.css$/,
loader: 'style!css?modules&localIdentName=[name]---[local]---[hash:base64:5]'
}]
}
};
Thanks.
MSSQL server connection libraries are not client-side javascript libraries. There is absolutely no way you can make TCP SQL connections from a web browser, even if you wrote your own library.
For security reasons, you would never want to allow client-side access to the SQL Server. You need to spin up server-side environment (e.g. Node/Express) to expose an API to the client applications.