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

fix: exclude neovim from webpack module. #4126 #4169

Merged
merged 1 commit into from
Oct 14, 2019
Merged

fix: exclude neovim from webpack module. #4126 #4169

merged 1 commit into from
Oct 14, 2019

Conversation

jpoon
Copy link
Member

@jpoon jpoon commented Oct 14, 2019

What this PR does / why we need it:
Excludes neovim module from whatever magic webpack is doing.

Which issue(s) this PR fixes
#4126

Special notes for your reviewer:
We need better tests, but I'm not even sure how we can even test this on Travis...

@jpoon jpoon merged commit 200c17f into master Oct 14, 2019
@jpoon jpoon deleted the fix-neovim branch October 14, 2019 07:19
@jpoon
Copy link
Member Author

jpoon commented Oct 14, 2019

Oh dammit. That did not work. Need to revert this commit and the release.

Activating extension `vscodevim.vim` failed:  Cannot find module 'neovim'

Probably worked cause module was available locally.

jpoon pushed a commit that referenced this pull request Oct 14, 2019
@jpoon jpoon mentioned this pull request Oct 14, 2019
@jpoon
Copy link
Member Author

jpoon commented Oct 14, 2019

Argh, I should have read the docs a bit better.

https://webpack.js.org/configuration/externals/

Instead, the created bundle relies on that dependency to be present in the consumer's environment. 

It was true in my case, but obviously on distribution this won't work.

jpoon added a commit that referenced this pull request Oct 14, 2019
* Revert "fix: exclude neovim from webpack module. #4126 (#4169)"

This reverts commit 200c17f.

* bump version
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.

1 participant