Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

using with angular 6

Open
#243 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
angular, javascript, sqlite
Domain
database, frontend

Research direction

Reproduce the Angular 6 build after installing @types/sql.js and sql.js, using the reported errors from node_modules/sql.js/js/sql.js as the starting point. Check whether the package can be resolved in that environment; done means the build no longer reports missing crypto, fs, and path modules.

Written by the indexing model from the issue text.

Description

Hi
I want to use this package with angular 6
I added the types and also sql
npm install --save @types/sql.js
npm install --save sql.js
but i get the following error:
[ng] Module not found: Error: Can't resolve 'crypto' in 'D:\current_projects\android Quran 2\ionic\Quran\node_modules\sql.js\js'
[ng] ERROR in ./node_modules/sql.js/js/sql.js
[ng] Module not found: Error: Can't resolve 'fs' in 'D:\current_projects\android Quran 2\ionic\Quran\node_modules\sql.js\js'
[ng] ERROR in ./node_modules/sql.js/js/sql.js
[ng] Module not found: Error: Can't resolve 'path' in 'D:\current_projects\android Quran 2\ionic\Quran\node_modules\sql.js\js'

Dominant language
JavaScript
Stars
13.7k
Forks
1.1k
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from sql-js/sql.js

All issues in sql-js/sql.js

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.