Skip to content
This repository was archived by the owner on Mar 5, 2025. It is now read-only.

NPM management of deployed front-end libraries #333

Closed
danepowell opened this issue Aug 29, 2016 · 2 comments
Closed

NPM management of deployed front-end libraries #333

danepowell opened this issue Aug 29, 2016 · 2 comments
Labels
Enhancement A feature or feature request

Comments

@danepowell
Copy link
Contributor

BLT supports managing NPM dev dependencies via a theme's package.json file. You can easily define frontend hooks in project.yml that will install these dependencies during the build process. The libraries themselves (in node_modules) then get stripped before deployment (they are specifically excluded by BLT and also in the .gitignore in the deploy artifact.)

This is problematic for third-party frontend libraries that should be deployed, such as select2. Right now you can still add these as non-dev dependencies to your project.yml and run npm install --no-dev as a post-deploy hook, but the gitignore will still exclude them.

@grasmash
Copy link
Contributor

Let's not gitignore them then.

danepowell added a commit to danepowell/blt that referenced this issue Aug 29, 2016
@danepowell
Copy link
Contributor Author

Yeah that should do the trick.

@grasmash grasmash added the Enhancement A feature or feature request label Sep 1, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Enhancement A feature or feature request
Projects
None yet
Development

No branches or pull requests

2 participants