-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
npm run build failure #123
Comments
Thanks to https://stackoverflow.com/a/77676983, I was able to complete the build. However, now that I have the extension running in my browser it gets stuck on `Looking up definitions for ...' when I do the search for an acronym. I'm running locally, reading the acronyms from dist/glossary.json and I confirmed that the Acronym I'm looking for is present in my glossary.json file. Any thoughts on how to address that? UPDATE: Figured it out. It was a trailing comma. Updated it in src/glossary.json and ran |
I'm keeping this issue open till someone from Capital One has confirmed that the stackoverflow link provides the correct solution and then I (or someone else) raises a PR to update Also, if someone from Capital One can update the dependency tree to eliminate the need for me to use |
What version of node are you running and can you share the full stacktrace? |
Note: I was using
❗ ❗ ❗ Now, moving on to the actual running. When I execute
|
Hello - I'm a former C1 Associate and trying to use this extension, but I'm unable to build it.
npm run build
fails with the error:./src/polyfills.ts:64:0-27 - Error: Module not found: Error: Package path ./dist/zone is not exported from package acronym-decoder/node_modules/zone.js (see exports field in acronym-decoder/node_modules/zone.js/package.json)
Command used to install:
bash-3.2$ npm install --legacy-peer-deps --verbose
Any clue what may be going wrong here?
The text was updated successfully, but these errors were encountered: