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

WIP npm assets #3

Conversation

iarna
Copy link

@iarna iarna commented Dec 28, 2017

This will land in npm w/ multiple commits, but for our purposes here squashing seemed best.

Installation

  • npm i installs from assetDependencies in package.json and assets section of package-lock.json
  • Don't install assets: npm i --no-assets, npm i --only=prod, npm i --only=dev
  • Only install assets: npm i --only=assets

Mutation

  • npm asset install asset-name npm a i asset-name
  • npm asset rm asset-name

Listing

  • npm asset ls

Asset Rewriting

This is currently the super naive implementation using regexp from assetize.

TODO

  • Replace regexp in asset rewriting with use of JS parser.

actions: Add support for asset related actions

install: Add new assets config options

actions: Only report the number of actions we'll run

copy-tree: Copy assets list

diff-trees: Generate asset diffs

install/deps: Remove unused third argument to doesChildVersionMatch

install/deps: Pass in log to removeObsoleteDep from resolveWithNewModule

install/deps: Add asset resolution

install: Resolve assets

assets

shrinkwrap: fix verb checkPackageFile → readPackageFile

install: Allow more general reporting of actions against arguments
@ceejbot ceejbot merged this pull request into chrisdickinson:you-cant-spell-ex-mea-sententia-without-e-s-m Jan 12, 2018
ceejbot pushed a commit that referenced this pull request Jan 12, 2018
Remove a pointless adapter frame  by fixing up the function's formal
parameter count.  Before:

    frame #0: 0x000033257ea446d5 onParserExecute(...)
    frame #1: 0x000033257ea3b93f <adaptor>
    frame #2: 0x000033257ea41959 <internal>
    frame #3: 0x000033257e9840ff <entry>

After:

    frame #0: 0x00000956287446d5 onParserExecute(...)
    frame #1: 0x0000095628741959 <internal>
    frame #2: 0x00000956286840ff <entry>

PR-URL: nodejs#17693
Reviewed-By: Anna Henningsen <anna@addaleax.net>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Daniel Bevenius <daniel.bevenius@gmail.com>
Reviewed-By: Khaidi Chu <i@2333.moe>
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.

2 participants