shopify / rollup-plugin-remap Goto Github PK

License: MIT License

JavaScript 100.00%

rollup-plugin-remap's Introduction

rollup-plugin-remap

Plugin to remap imported modules to other file paths. Useful for conditional compilation, ie: remapping development focused modules to a noop during a production build.

Examples

In this example, we're remapping a logger module to a noop module during a production build of a project.

rollup.config.js

const plugins = [];

if (process.env.BUILD_MODE === 'proudction') {
  plugins.push(remap({
    originalPath: 'src/logger.js',
    targetPath: 'src/noop.js'
  }));
}
export default {
  entry: 'src/someModule.js',
  plugins
}

Would remap the following import to a file called src/noop.js.

src/someModule.js

import logger from './logger';

export default function doStuff() {
  // ...
  // do some stuff
  // ...

  logger('I did some stuff');
}

rollup-plugin-remap's People

Contributors

Stargazers

Watchers

Forkers

swivelgames qpc-github

rollup-plugin-remap's Issues

Action required: CircleCI v1.0 is EOL, this repo is impacted

This repository relies on CircleCI v1.0 which will be shut down on Aug 31st.

cc @minasmart

Update public package publish config

👋 Shipit has recently been updated to support private npm package publishing. The @shopify scope for npm packages in Shipit now references our internal PackageCloud registry by default. You can read more about this here.

This library, however, uses a Shipit deploy override in shipit.yml which prevents Shipit from automating the public/private registry selection.

Since this library is public, please update the package.json by specifying the public registry in the publishConfig setting.

"publishConfig": {
  "access": "public",
  "@shopify:registry": "https://registry.npmjs.org/"
}

If possible, we also recommend removing the shipit.yml deploy override to leverage Shipit’s default deployment steps.

Missing classification

Owners: @Shopify/operational-excellence (This repo has no owners)
Service: rollup-plugin-remap/production

Please set a classification.

You can add it in service.yml, under the key classification.

Refer to the detailed documentation for more information.

rollup-plugin-remap: Classification Check

Classification Check

TL;DR

1st party software must have a business impact classification. See our list of classification to help you determine the classification of your application.

Why is this being asked?

It's critical that we understand the business impact of the software we write. The classification of your service determines the level of support you must provide as owners and helps us set standards.

What will happen if it doesn't get done within the expected timeframe?

This is mandatory. If this is not done you won't be able to have any runtimes.

When does it need to get done?

At the latest, this should be done before 2021-07-22.

This doesn't apply to my service. What do I do?

First, leave a comment explaining why it doesn't apply. Then, leave another comment as /not_applicable, and close the issue.
If you change your mind, make sure to comment any reason and reopen the issue.

I have questions/concerns about this

Please contact the Production Excellence team using Slack at #production-excellence-team.
Your service: rollup-plugin-remap/production
Owners: