search

strongloop / strong-globalize

strong-globalize is built on Unicode CLDR and jquery/globalize and implements automatic extraction of strings from JS source code and HTML templates, lint the string resource, machine-translate them in seconds. In runtime, it loads locale and string resource into memory and provides a hook to persistent logging.
Other
25 stars 16 forks source link

`slt-globalize -d` doesnt extract strings from the node_modules #136

Closed aastha93 closed 5 years ago

aastha93 commented 6 years ago 
--- max depth: unlimited
--- cloned: 0 txt
--- scanned: 9041 js, 0 html 
--- skipped: 380 js, 0 html 
--- extracted: 597 msges, 7090 words, 41889 characters**

380 js files skipped. when I try to run deep extraction

dhmlau commented 6 years ago

@aastha93 , are you using v4 of this module?

aastha93 commented 6 years ago

@dhmlau I am using version 3.2.0

dhmlau commented 6 years ago

@aastha93 , sorry that I haven't tried with -d option before. I assume the environment variable STRONGLOOP_GLOBALIZE_MAX_DEPTH is valid? References: http://strongloop.github.io/strong-globalize/#deep-string-resource-extraction

@raymondfeng , could you please help?

b-admike commented 6 years ago

@aastha93 can you update your version to latest released version (v4.1.0) and try again? can you please give us steps you took to reproduce the issue?

aastha93 commented 6 years ago

@b-admike I have installed the version 4.1.0 and suddenly the slt-globalize command is not available.

bajtos commented 6 years ago

The report looks legitimate to me, however I need more details to be able to tell why those 380 files were skipped. How can we reproduce the problem on our local machines?

For example, if you know which files were skipped and some of the skipped files are coming from public packages available on npmjs.org, then you can try the following scenario to see if it reproduces the problem:

Then tell us the name of this problematic package :)

I have installed the version 4.1.0 and suddenly the slt-globalize command is not available.

In 4.0, we moved slt-globalize to a new package strong-globalize-cli in order to reduce the size of application dependencies. (Typically, applications depend on strong-globalize runtime only, the CLI is either installed globally or as a dev-dependency.)