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

Allow custom env for Webpacker #1350

Closed
wants to merge 1 commit into from

Conversation

tricknotes
Copy link
Contributor

The Rails defined custom env is allowed by #1304.
However Webpacker custom env is not allowed for now.

/Users/tricknotes/dummy-app/node_modules/@rails/webpacker/package/config.js:16
    delete defaults.extensions
           ^

TypeError: Cannot convert undefined or null to object

This commit allows using user defined env for Webpacker.

The Rails defined custom env is allowed by rails#1304.
However Webpacker custom env is not allowed for now.

```
/Users/tricknotes/dummy-app/node_modules/@rails/webpacker/package/config.js:16
    delete defaults.extensions
           ^

TypeError: Cannot convert undefined or null to object
```

This commit allows using user defined env for Webpacker.
@arempe93
Copy link

for anyone waiting for this to get into a release, just run:

$ yarn remove @rails/webpacker
$ yarn add git://github.com/tricknotes/webpacker.git#allow-costom-env

doing that allowed me to deploy to qa/staging envs with no other changes

@haffla
Copy link
Contributor

haffla commented Mar 14, 2018

I'm pinned down to 3.2.x waiting for this 💅

@gauravtiwari
Copy link
Member

Thanks @tricknotes again for your contribution. Please see #1359

@tricknotes tricknotes deleted the allow-costom-env branch March 21, 2018 02:33
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