Skip to content

Library not intended for use in a browser? #5

@aweber1

Description

@aweber1

Hello,

I'm trying to integrate this library into an application that is running in the browser. However, there are Node module dependencies preventing that from happening. In particular, the fs module.

import contentstack from '@contentstack/management';

results in a Module note found: can't resolve 'fs' error message.

I have verified that the import statement is resolving to node_modules/@contentstack/management/dist/web/contentstack-management.js. However, it appears that the web version of the library build contains a require("fs") statement.

Is this library not intended for use in a browser? If so, I would recommend clearly stating that in the readme. However, if it is intended to be used in the browser, I think some refactoring may be in order to remove the dependencies on Node core modules.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions