-
Notifications
You must be signed in to change notification settings - Fork 538
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
No package.json #3
Comments
There's a package.json here: https://github.com/kubernetes-client/javascript/blob/master/node/package.json I don't think we need a top-level one, do we? |
ok, it's a little uncommon, though. so you might see more people asking about it. |
The motivation was because I want both a Thanks! |
It would make sense to me if there were different But the confusion for me might have been caused by the ts files sitting in the same directory as the |
I'm definitely new to packaging a TS library, if you have pointers to canonical examples, I'm happy to re-factor the directory layout.
Thanks!
…________________________________________
From: Sven Efftinge <notifications@github.com>
Sent: Monday, January 8, 2018 12:35 PM
To: kubernetes-client/javascript
Cc: Brendan Burns; Comment
Subject: Re: [kubernetes-client/javascript] No package.json (#3)
It would make sense to me if there were different package.json for the code and the examples, but I only see one package.json. You can specify in package.json that examples should not be published.
But the confusion for me might have been caused by the ts files sitting in the same directory as the package.json. They usually sit in some sort of source folder, so you can separate them from .js and .d.ts files. And the package.json in the parent.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fkubernetes-client%2Fjavascript%2Fissues%2F3%23issuecomment-356088061&data=02%7C01%7Cbburns%40microsoft.com%7C539281191395498fa0b708d556d751d6%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636510405143215501&sdata=nqGvzyHDI0S0kSBjwEeulu6s1QZ%2FhywU4BdRsWksZWM%3D&reserved=0>, or mute the thread<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAFfDghU0tOJ4LPeaod13sk8s2WdTM4dxks5tInv_gaJpZM4RRcQE&data=02%7C01%7Cbburns%40microsoft.com%7C539281191395498fa0b708d556d751d6%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636510405143215501&sdata=LzxUfSXYpqqbEZ%2BVHQS7jyTPAVeOHo1vBQ%2B%2Bf%2FMMLLE%3D&reserved=0>.
|
…nt#3) - renamed ‘node’ to ‘node-client’ to better match the package name - moved source code to src folder - removed some unneeded libs from package.json - fixed some imports - updated .gitignore
It was easier to just make a proposal, than explaining it :) Feel free to take anything you find useful and please ask if you have questions. |
Some improvements for the overall project layout (see #3)
There is no package.json.
The text was updated successfully, but these errors were encountered: