This is the very first thing I've ever entered into github so there is a huge risk I am committing [no pun] an error in protocol so for that let me apologize first. If I have done, just let me know.
The package.json for the example (msal-react-lite/example/package.json) has relative paths (../) that seem to confuse npm start.
For example, I see: "start": "node ../node_modules/react-scripts/bin/react-scripts.js start",
instead of the more typical: "start": "react-scripts start",
I've had a hack but I can't get the scripting and dependency detection working properly.
There is every chance it is my ignorance responsible but I don't know where to start looking since the npm stuff has always just "worked"; I use it without really understanding the subtleties.
I am clearly missing something fundamental. Any hints?
BTW, I think this component is exactly what we need at the moment for some work we are doing which is why I'm risking annoying you with this.
Thanks for the effort in the build!
This is the very first thing I've ever entered into github so there is a huge risk I am committing [no pun] an error in protocol so for that let me apologize first. If I have done, just let me know.
The
package.jsonfor theexample(msal-react-lite/example/package.json) has relative paths (../) that seem to confusenpm start.For example, I see:
"start": "node ../node_modules/react-scripts/bin/react-scripts.js start",instead of the more typical:
"start": "react-scripts start",I've had a hack but I can't get the scripting and dependency detection working properly.
There is every chance it is my ignorance responsible but I don't know where to start looking since the
npmstuff has always just "worked"; I use it without really understanding the subtleties.I am clearly missing something fundamental. Any hints?
BTW, I think this component is exactly what we need at the moment for some work we are doing which is why I'm risking annoying you with this.
Thanks for the effort in the build!