The version 0.3.0 is not covered by your current version range.
If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.
It might be worth looking into these changes and trying to get this project onto the latest version of microbundle.
If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.
Release Notes0.3.0
Features
Add support for JSX (+ --jsx pragma option) (#13, thanks @wcastand)
Add support for tagged template strings (#29, thanks @rtorr)
Add CSS support with PostCSS and Autoprefixer (#30, thanks @tknipfer)
FAQ and help
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).
Version 0.3.0 of microbundle was just published.
The version 0.3.0 is not covered by your current version range.
If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.
It might be worth looking into these changes and trying to get this project onto the latest version of microbundle.
If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.
Release Notes
0.3.0Features
--jsx
pragma option) (#13, thanks @wcastand)--inline all
option so it inlines modules fromnode_modules
(#33, thanks @ColinRTaylor)"browser"
entries in package.json, add--target node
option to bypass (#38, thanks @kevlened)node_modules
(#24, thanks @jescalan)"mangle"
field to package.json to allow custom property mangling--name
option to customize export name (#10, thanks @msfragala)snake_case
topascalCase
for auto module names (#15, thanks @msfragala)Bug Fixes
Commits
The new version differs by 42 commits.
d52bd6c
0.3.0
79c8cb9
oss.ninja 🥋
2054b0a
Only extract & write out CSS files once.
2dcd669
Dedupe entries.
f5b61e7
Allow specification of Uglify's
mangle
option in thepackage.json
, and use it to enable advanced property mangling.b58b980
Fix error messages
73a564b
Update dependencies. Fixes #42
e9683e1
Merge pull request #38 from kevlened/master
708ec4d
Tab to space fix in README
65dc28f
Invert target option logic
5f7f805
Add target environment option
90d02e6
Merge pull request #32 from lukeed/cli
d8162d5
Merge pull request #33 from ColinRTaylor/pr/inline-all
1b315c7
k fine.
cabd4d1
refactor/simplify
run
invoc;There are 42 commits in total.
See the full diff
FAQ and help
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper bot :palm_tree: