-
Notifications
You must be signed in to change notification settings - Fork 122
directory gets created outside of messagesDir #23
Comments
ah it seems it's actually following the symlinks:
|
Is there a way to protect the path so it never gets out of the messagesDir? |
I don't understand the problem. What are the values for: the dir you're running Babel in, the configured |
Run babel from: |
Sorry I also meant to ask the source path to a JS file. Is it not under What I'm thinking is that the problem is happening here: https://github.com/yahoo/babel-plugin-react-intl/blob/master/src/index.js#L157-L161 If you can step through those lines while running Babel that might show where the issue is. I haven't seen this happen before so I'm trying to figure out what's different with the inputs to this code that are resulting in the unexpected output. |
Some of the source files are under the root dir of the app ( |
I've never tried to compile code in |
Here is the output from my logging:
|
I'm using browserify with this transform:
and this is my
|
This is a directory listing of the app's node modules:
The symbolic links are because of the usage of When I don't use a link, all is fine. However, I need to use a link so I can edit the |
If you can edit the plugin code locally to get it to work within your setup, feel free to send a PR. When I get a chance I'll try to setup a simple project to reproduce that uses symlinks to see if I can reproduce. |
This should now be fixed with the changes from #32 |
thanks! |
I have an app that links to an SDK using npm link. This all works fine, except for babel-plugin-react-intl generating a directory outside of messagesDir.
So the app.json gets created in the correct location:
build/messages/app.json
but the .json files of the SDK (which is in node_modules/boundlessgeo-sdk) get generated in sdk in the root of the repo:
Any pointers to as why this might be happening? This is only when using npm link between app and SDK.
The text was updated successfully, but these errors were encountered: