WARNING: THIS SITE IS A MIRROR OF GITHUB.COM / IT CANNOT LOGIN OR REGISTER ACCOUNTS / THE CONTENTS ARE PROVIDED AS-IS / THIS SITE ASSUMES NO RESPONSIBILITY FOR ANY DISPLAYED CONTENT OR LINKS / IF YOU FOUND SOMETHING MAY NOT GOOD FOR EVERYONE, CONTACT ADMIN AT ilovescratch@foxmail.com
Skip to content

Bundling approach is problematic #42

@oliversalzburg

Description

@oliversalzburg

The README suggests that the npm pack approach is almost a great feature, but I disagree.

npm pack, or anything that uses fstream-npm is bad to rely on when dealing with a NodeJS project. Not only does it rely on .npmignore, a file we already have a different purpose for, it also ignores tons of files we might want to keep (our main issue are private modules). In fact, the ignore semantics are incredibly complicated.

This means that the bundles created from strider-ssh-deploy are not usable application snapshots. The result of which is that we have to manually create packages, put them into HTTP-accessible storage and download them on the production server all via custom scripts.

I would propose that a simply tar czf package.tgz * is used in place of npmd-pack.

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