inrupt / inrupt/solid-client-authn-js
bundle is a 404 when running `npm run dev-script`
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 77
- Forks
- 49
- Avg merge
- 18h 20m
- Merged PRs (30d)
- 32
Description
npm run dev-script starts a web server on port 3001, but the browser then says solid-auth-fetcher-bundle.js is a 404.
Running npm run build works around that, but then the error in the browser console is:
solid-auth-fetcher.bundle.js:144 Uncaught (in promise) Error: schema is invalid:
should have required property '.oidcIssuer',
should have required property '.webId',
should match exactly one schema in oneOf
at Object.e.default (solid-auth-fetcher.bundle.js:144)
at f.loginHelper (solid-auth-fetcher.bundle.js:205)
at f.login (solid-auth-fetcher.bundle.js:205)
at Object.e.login (solid-auth-fetcher.bundle.js:190)
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by inspecting the npm configuration behind npm run dev-script and npm run build, then reproduce the missing solid-auth-fetcher-bundle.js in the browser. Trace the login path associated with the reported schema error. Done means the development script serves the bundle and the reported login error no longer occurs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- authentication, build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100