You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
1/2A quarter days workbugSomething isn't workingpatchDevelopment requiring a patch version changespikeInvestigation into the topic described by the issue
This should start for development without error. If not building before the config.json file is not available.
(node:204436) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, open 'C:\Users\wwelling\Development\work\tamu-library-components\dist\bundle\config.json'
(Use `node --trace-warnings ...` to show where the warning was created)
(node:204436) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:204436) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
Current workaround:
npm install
npm run build
npm start
Needs to be reproduced
The text was updated successfully, but these errors were encountered:
ghost
changed the title
TL Components development start fails to find config.json
TAMU library components development start fails to find config.json
Sep 2, 2021
jeremythuff
added
bug
Something isn't working
patch
Development requiring a patch version change
1/2
A quarter days work
spike
Investigation into the topic described by the issue
labels
Oct 27, 2021
1/2A quarter days workbugSomething isn't workingpatchDevelopment requiring a patch version changespikeInvestigation into the topic described by the issue
This should start for development without error. If not building before the config.json file is not available.
Current workaround:
Needs to be reproduced
The text was updated successfully, but these errors were encountered: