Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Release build in npm #103

Open
SebastianStehle opened this issue Apr 14, 2020 · 4 comments
Open

Release build in npm #103

SebastianStehle opened this issue Apr 14, 2020 · 4 comments

Comments

@SebastianStehle
Copy link

Hi,

your npm package contains basically the same files like this repo, including all the dependencies like gulp that i don't need. It would be great if you could create a release package with just the assets or so.

@radhikamehraa
Copy link

Can you further detail out the issue for me to resolve am unaware of koding/coding

@rarestoma
Copy link
Contributor

Hi @SebastianStehle,

Thank you for working with our products.

I will discuss on my team and see how can we make those changes to the npm package.

Thank you,
Rares

@SebastianStehle
Copy link
Author

I am not an npm expert. Perhaps you can just declare the dependencies as peer dependencies? The problem is that some of your gulp packages have git dependencies and I don't have git available in my build server process and also do not want to have all these dependencies.

@rarestoma
Copy link
Contributor

Hi @SebastianStehle,

We will take a closer look and see how can we add such a package on npm.

Thank you,
Rares

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants