I've been working on setting up msal for use with nodejs. My goal is to verify that emails are successfully received by test users in end-to-end webdriverio tests.
Following the npm msal guide here, I made good progress but ran into some errors while running:
npm run build
.
npm run build
> [email protected] build C:\Users\User\TestAutomation\node_modules\msal
> npm run clean && npm run doc && npm run build:modules && webpack && grunt && npm test
...
(ERROR messages related to Src files and loaders)
...
ERROR in ./src/UserAgentApplication.ts
Module parse failed: Unexpected token (39:8)
You may need an appropriate loader to handle this file type.
| import { AuthorityFactory } from "./AuthorityFactory";
|
| declare global {
| interface Window {
| msal: Object;
@ ./src/index.ts 1:0-62 8:0-51
@ multi ./src/index.ts
npm ERR! code ELIFECYCLE
npm ERR! errno 2
npm ERR! [email protected]-->
failed at script (more logging output)
...
This appears to be a babel error:
You may need an appropriate loader to handle this file type.
However, I'm not sure how to resolve it. I attempted installing Babel as well, unsure if it needs to be integrated somewhere.
As I am relatively new to these tools, it's likely a simple mistake. After spending some time troubleshooting, I figured reaching out for assistance would be beneficial. If I manage to solve it, I'll update this post.
A big thank you to the MS team for providing msal.
Update: Including webpack.config.js
The webpack.config.js file autogenerated by npm install msal:
var path = require("path");
var webpack = require("webpack");
var PATHS = {
entryPoint: path.resolve(__dirname, 'src/index.ts'),
bundles: path.resolve(__dirname, 'dist'),
}
var config = {
// Configuration details
}
module.exports = config;