Thank you for this attempt to bring sanity to publishing a package for reuse on npm.
The install, as of ten minutes ago, gives a number of warnings that frighten me. Full output below, but in short:
this package has been deprecated
Browserslist 2 could fail on reading Browserslist >3.0 config used in other tools
I wrote this module a very long time ago; you should use something else.
I'm seeing a lot of build update/upgrade type issues in the list from a "greenkeeper" bot. Perhaps those issues and auto-pr's will clear this up. In any case, if this issue post is unhelpful noise, please pardon (I see 66 open issues). Feel free to close.
Apology that I don't have the skills to make a PR. This node ecosystem just kills me. Cross compiling C code was easier than this.
Thank you again.
~/Documents/p.site$ mkdir dltem
~/Documents/p.site$ cd dltem
~/Documents/p.site/dltem$ yarn init
yarn init v1.17.0
question name (dltem):
question version (1.0.0):
question description:
question entry point (index.js):
question repository url:
question author:
question license (MIT):
question private:
success Saved package.json
✨ Done in 6.84s.
~/Documents/p.site/dltem$ yarn add --dev microbundle
yarn add v1.17.0
info No lockfile found.
[1/4] 🔍 Resolving packages...
warning microbundle > @babel/polyfill@7.4.4: 🚨 As of Babel 7.4.0, this
package has been deprecated in favor of directly
including core-js/stable (to polyfill ECMAScript
features) and regenerator-runtime/runtime
(needed to use transpiled generator functions):
> import "core-js/stable";
> import "regenerator-runtime/runtime";
warning microbundle > rollup-plugin-postcss > cssnano > autoprefixer > browserslist@1.7.7: Browserslist 2 could fail on reading Browserslist >3.0 config used in other tools.
warning microbundle > rollup-plugin-postcss > cssnano > postcss-merge-rules > browserslist@1.7.7: Browserslist 2 could fail on reading Browserslist >3.0 config used in other tools.
warning microbundle > rollup-plugin-buble > buble > os-homedir@2.0.0: This is not needed anymore. Use `require('os').homedir()` instead.
warning microbundle > rollup-plugin-postcss > cssnano > postcss-merge-rules > caniuse-api > browserslist@1.7.7: Browserslist 2 could fail on reading Browserslist >3.0 config used in other tools.
warning microbundle > rollup-plugin-postcss > cssnano > postcss-minify-selectors > postcss-selector-parser > flatten@1.0.2: I wrote this module a very long time ago; you should use something else.
[2/4] 🚚 Fetching packages...
[3/4] 🔗 Linking dependencies...
warning "microbundle > rollup-plugin-typescript2@0.19.3" has incorrect peer dependency "rollup@>=0.68.0".
[4/4] 🔨 Building fresh packages...
success Saved lockfile.
success Saved 323 new dependencies.
Thank you for this attempt to bring sanity to publishing a package for reuse on npm.
The install, as of ten minutes ago, gives a number of warnings that frighten me. Full output below, but in short:
I'm seeing a lot of build update/upgrade type issues in the list from a "greenkeeper" bot. Perhaps those issues and auto-pr's will clear this up. In any case, if this issue post is unhelpful noise, please pardon (I see 66 open issues). Feel free to close.
Apology that I don't have the skills to make a PR. This node ecosystem just kills me. Cross compiling C code was easier than this.
Thank you again.
Here is ~/Documents/p.site/dltem/package.json: