Skip to content

webpack configuration and devDependencies usage #164

@joshua-dean

Description

@joshua-dean

See discussion here and here.

Currently "minimizing"/"uglifying" logic in webpack.config.js is commented out, so the build process should probably revisited and documented (maybe webpack isn't even needed?). a

Conversation stems from package.json missing typescript as a dependency, but as ULabel (currently) gets packed with webpack, technically everything should be in devDependencies as it all gets packed when pushed to npm. This stackoverflow answer indicates there's some nice categories when using npm itself, so maybe that is worth looking into.

tl;dr Laziest solution is chuck everything in devDependencies and clean up webpack.config.js.

Metadata

Metadata

Assignees

No one assigned

    Labels

    refactorThe code should be better

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions