Skip to content

Comments

feat: SDK-713 npm package structure for userlib#370

Merged
hansl merged 4 commits intomasterfrom
hansl/npm-package
Feb 17, 2020
Merged

feat: SDK-713 npm package structure for userlib#370
hansl merged 4 commits intomasterfrom
hansl/npm-package

Conversation

@hansl
Copy link
Contributor

@hansl hansl commented Feb 10, 2020

This looks like this:

image

@hansl hansl force-pushed the hansl/npm-package branch 2 times, most recently from 99997f7 to 4ffb3ba Compare February 10, 2020 23:44
@hansl hansl changed the title feat: npm package structure for userlib feat: SDK-713 npm package structure for userlib Feb 10, 2020
@hansl hansl force-pushed the hansl/npm-package branch from 4ffb3ba to fc18386 Compare February 12, 2020 01:17
@hansl hansl force-pushed the hansl/npm-package branch from fc18386 to c75570c Compare February 14, 2020 20:40
@hansl hansl marked this pull request as ready for review February 14, 2020 21:13
@hansl hansl requested a review from a team February 14, 2020 21:13
@hansl hansl requested a review from a team as a code owner February 14, 2020 21:13
Copy link
Contributor

@chenyan-dfinity chenyan-dfinity left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Two questions:

  1. Does this mean userlib is now semi-open-source? Do we need explicit approval for this?
  2. Can you write a README for internal engineers on how to develop userlib? We used to do npm run bundle and copy dist to cache. I think now it's going to change to something else.

@eftychis
Copy link
Contributor

Yes I think some readme is necessary here. Also some notes on next steps.

@eftychis
Copy link
Contributor

Otherwise, this looks fine to me minus minor notes above.

@hansl
Copy link
Contributor Author

hansl commented Feb 14, 2020

Does this mean userlib is now semi-open-source? Do we need explicit approval for this?

This enables this, but does not release it yet.

Can you write a README for internal engineers on how to develop userlib? We used to do npm run bundle and copy dist to cache. I think now it's going to change to something else.

Sure!

Copy link
Contributor

@eftychis eftychis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If you add the README for development then this LGTM.

Thanks Hans 😎

@hansl
Copy link
Contributor Author

hansl commented Feb 17, 2020

@eftychis @chenyan-dfinity PTAL.

Copy link
Contributor

@chenyan-dfinity chenyan-dfinity left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Thanks.

@hansl hansl merged commit 7fc2cdf into master Feb 17, 2020
@hansl hansl deleted the hansl/npm-package branch February 17, 2020 18:50
hansl pushed a commit that referenced this pull request Feb 17, 2020
hansl pushed a commit that referenced this pull request Feb 17, 2020
hansl pushed a commit that referenced this pull request Feb 19, 2020
hansl pushed a commit that referenced this pull request Feb 28, 2020
dfinity-bot added a commit that referenced this pull request Aug 28, 2020
## Changelog for advisory-db:
Branch: 
Commits: [rustsec/advisory-db@47d12507...c341943a](rustsec/advisory-db@47d1250...c341943)

* [`91aeb3b0`](rustsec/advisory-db@91aeb3b) Suggest lz-fear as an alternative to lz4-compress
* [`002af101`](rustsec/advisory-db@002af10) failure: add informational "unmaintained" advisory ([RustSec/advisory-db⁠#368](http://r.duckduckgo.com/l/?uddg=https://github.com/RustSec/advisory-db/issues/368))
* [`1d3ca115`](rustsec/advisory-db@1d3ca11) Assigned RUSTSEC-2020-0036 to failure ([RustSec/advisory-db⁠#369](http://r.duckduckgo.com/l/?uddg=https://github.com/RustSec/advisory-db/issues/369))
* [`df8a0c46`](rustsec/advisory-db@df8a0c4) RUSTSEC-2020-0036: add fehler ([RustSec/advisory-db⁠#370](http://r.duckduckgo.com/l/?uddg=https://github.com/RustSec/advisory-db/issues/370))
mergify bot pushed a commit that referenced this pull request Aug 28, 2020
## Changelog for advisory-db:
Branch: 
Commits: [rustsec/advisory-db@47d12507...c341943a](rustsec/advisory-db@47d1250...c341943)

* [`91aeb3b0`](rustsec/advisory-db@91aeb3b) Suggest lz-fear as an alternative to lz4-compress
* [`002af101`](rustsec/advisory-db@002af10) failure: add informational "unmaintained" advisory ([RustSec/advisory-db⁠#368](http://r.duckduckgo.com/l/?uddg=https://github.com/RustSec/advisory-db/issues/368))
* [`1d3ca115`](rustsec/advisory-db@1d3ca11) Assigned RUSTSEC-2020-0036 to failure ([RustSec/advisory-db⁠#369](http://r.duckduckgo.com/l/?uddg=https://github.com/RustSec/advisory-db/issues/369))
* [`df8a0c46`](rustsec/advisory-db@df8a0c4) RUSTSEC-2020-0036: add fehler ([RustSec/advisory-db⁠#370](http://r.duckduckgo.com/l/?uddg=https://github.com/RustSec/advisory-db/issues/370))
gobengo pushed a commit that referenced this pull request Sep 1, 2020
## Changelog for advisory-db:
Branch: 
Commits: [rustsec/advisory-db@47d12507...c341943a](rustsec/advisory-db@47d1250...c341943)

* [`91aeb3b0`](rustsec/advisory-db@91aeb3b) Suggest lz-fear as an alternative to lz4-compress
* [`002af101`](rustsec/advisory-db@002af10) failure: add informational "unmaintained" advisory ([RustSec/advisory-db⁠#368](http://r.duckduckgo.com/l/?uddg=https://github.com/RustSec/advisory-db/issues/368))
* [`1d3ca115`](rustsec/advisory-db@1d3ca11) Assigned RUSTSEC-2020-0036 to failure ([RustSec/advisory-db⁠#369](http://r.duckduckgo.com/l/?uddg=https://github.com/RustSec/advisory-db/issues/369))
* [`df8a0c46`](rustsec/advisory-db@df8a0c4) RUSTSEC-2020-0036: add fehler ([RustSec/advisory-db⁠#370](http://r.duckduckgo.com/l/?uddg=https://github.com/RustSec/advisory-db/issues/370))
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

Successfully merging this pull request may close these issues.

4 participants