Injection token IDB_DB_NAME is not exposed

[joeskeen]

Checks before posting an issue

• I have read all the library's documentation:
  • README
  • CHANGELOG
  • MIGRATION
  • /docs
• I have checked in already:
  • opened issues
  • closed issues
  • questions answered in the new "Discussions" tab
• I understand I am writing to a human being, doing this project unpaid
• I will be involved in my own issue, by answering questions and informing if the issue is resolved

Configuration

• @ngx-pwa/local-storage version: 20.0.1
• Angular version (ng version):

Angular CLI: 20.3.7
Node: 22.18.0
Package Manager: npm 10.9.3
OS: linux x64
    

Angular: 20.3.7
... build, cli, common, compiler, compiler-cli, core, forms
... platform-browser, router, service-worker

Package                      Version
------------------------------------
@angular-devkit/architect    0.2003.7
@angular-devkit/core         20.3.7
@angular-devkit/schematics   20.3.7
@schematics/angular          20.3.7
rxjs                         7.8.2
typescript                   5.9.3

Description of the issue

I'm needing to export/import the IndexedDb state in my application. I have a script to do that, but it requires the name of the database to export/import. I currently have 'ngStorage' hard-coded as the name of the DB in my code, but it appears that your provideIndexedDBDataBaseName function allows you to set a custom DB name. In the event that this occurs, there is no way to probe the module for the DB name, since IDB_DB_NAME is not exported (I just want to inject that token into my import/export service).

I am happy to put in a pull request for this if you would like!

[cyrilletuzi]

Hello, thank you for respecting for issue template. 👍🏻

Exposing things has consequences in a library, and it is intentional to not expose such internals. So before making such a choice, I would have to be sure it is for good reasons.

I am not sure to have fully understood your use case, but something feels strange in the global approach: all the elements are in the control of your application. I mean that the import/export service and the configuration of this lib (provideIndexedDBDataBaseName with eventually a custom database name) are done in your application side (not inside the lib). So 2 cases:

• either you know that the database name is not changed, so hard-coded ngStorage seems OK
• you know that the database name is changed, and in that case why not export const customDbName = 'test' and use it both for provideIndexedDBDataBaseName and your import/service?

Also note that there is already a way to retrieve some informations:

if (this.storage.backingEngine === 'indexedDB') {
  const { database, store, version } = this.storage.backingStore;
}

Does that make sense to you? Otherwise I would need to better understand your use case.