frozeman / meteor-build-client Goto Github PK

starfall@nx:~/workspace/foreach$ meteor-build-client /tmp/mbc
Bundling Meteor app...
Generating the index.html...

module.js:340
    throw err;
          ^
Error: Cannot find module '/home/starfall/workspace/foreach/tmp/mbc/bundle/star.json'

Looks like it tries to find a star.json by relative path :) Workaround:

starfall@nx:~/workspace/foreach$ meteor-build-client ../mbc -s settings/shipstation-prod.json -u https://shipstation.meteor.com/
Bundling Meteor app...
Generating the index.html...
Done!
-----
You can find your files in "/home/starfall/workspace/mbc".

It looks like meteor 1.3 clients require an additional property in the meteor_runtime_config.
"meteorEnv":{"NODE_ENV":"production"}}

If it doesn't find the property the client crashes at startup with a:

Uncaught TypeError: Cannot read property 'NODE_ENV' of undefined

It seems unfortunate that the meteor client would rely on the NODE_ENV property and maybe its just an oversight on their part that will be resolved by the time 1.3 releases - but its broken at the moment none the less.

I guess passing the additional property is a pretty simple change however since 1.3 is not officially released it might be premature.

Perhaps an option to pass additional runtime config fields would allow us to work around issues like this without requiring further code changes. Once 1.3 is release a more permanent change to the property would be appropriate.

I have run the command meteor-build-client ../build -p '' on a meteor project folder.
I keep getting the same issue

Bundling Meteor app...
Command failed: /bin/sh -c meteor build ../build --directory
Supply the server hostname and port in the --server option for mobile app
builds.

 undefined

Any help?
Thanks.

Once copied onto my server routing works fine if you hit the root url first, but not if you hit a root/charts

404 error.

Any way to get this working again?

XMLHttpRequest cannot load file:///sockjs/info?cb=xg7uuxnabr. 
Cross origin requests are only supported for protocol schemes: 
http, data, chrome, chrome-extension, https, chrome-extension-resource.

Looked through the source and did some diagnosing and it seems like the --server flag is not working?

And the solution provided DDPConnection = (Meteor.isClient) ? DDP.connect("http://localhost:3000/") : {};

Did not work for me and it seems like a dirty fix.

Please check

Files are getting generated but does not contains any script tags, only basic html

After running meteor-build-client (version 1.01), the index.html file is created but it does not include the js and css files the bundler generated.

Generating the index.html...

fs.js:760
  return binding.unlink(pathModule._makeLong(path));
                 ^
Error: EPERM, operation not permitted 'c:\Users\user\Projects\testMeteor\test_client\bundle\main.js'
    at Object.fs.unlinkSync (fs.js:760:18)
    at c:\Users\user\AppData\Roaming\npm\node_modules\meteor-build-client\meteor.js:45:20
    at Array.forEach (native)
    at deleteFolderRecursive (c:\Users\user\AppData\Roaming\npm\node_modules\meteor-build-client\meteor.js:40:15)
    at Object.module.exports.cleanUp (c:\Users\user\AppData\Roaming\npm\node_modules\meteor-build-client\meteor.js:165:9)
    at c:\Users\user\AppData\Roaming\npm\node_modules\meteor-build-client\main.js:84:20
    at null._onTimeout (c:\Users\user\AppData\Roaming\npm\node_modules\meteor-build-client\queue.js:41:11)
    at Timer.listOnTimeout [as ontimeout] (timers.js:110:15)

It looks like it's trying to delete a file that was created during the build. I don't know why permissions were set such that it couldn't delete it. I'm on a Windows 8.1 box, and I ran it under MSYS bash, if that helps.

test was my project directory and test_client was in the same directory as test, and it was my build directory.

Noticed these today on Windows and after hours pulling out my hair it seems it's a simple file name too long error.

Renaming to 1.js and 1.css fixed the issue

I'm trying to use this tool on a newly created app and when I open the index.html in the browser, Meteor is never defined and hence doesn't run the app at all.

I had to edit the index.html to have a . in front of the css href link and the script src files.

Even then, I'm still getting errors:

XMLHttpRequest cannot load file:///sockjs/info?cb=sh1vwpyq6g. Cross origin requests are only supported for protocol schemes: http, data, chrome, chrome-extension, https, chrome-extension-resource.w._start @ b3f39905266a5d98e7a045660ed3ec524ed47482.js:32(anonymous function) @ b3f39905266a5d98e7a045660ed3ec524ed47482.js:32

Uncaught NetworkError: Failed to execute 'send' on 'XMLHttpRequest': Failed to load 'file:///sockjs/info?cb=sh1vwpyq6g'.w._start @ b3f39905266a5d98e7a045660ed3ec524ed47482.js:32(anonymous function) @ b3f39905266a5d98e7a045660ed3ec524ed47482.js:32

For SSR:
https://docs.meteor.com/packages/server-render.html#Streaming-HTML

we have some dynamic data need insert in the onPageLoad, I have tried, but it did not work with the static file, is there a solution?

I'm having trouble compiling using the tool.

Both meteor-build-client ../build -p "" and meteor-build-client ../build2 -u http://localhost:8080 result in this HTML file which tries to load /undefined:

<html>
    <head>
        <link rel="stylesheet" type="text/css" class="__meteor-css__" href="/a9c351b0b865337742fa34ec4882eb46352b3755.css?meteor_css_resource=true">
        <script type="text/javascript">__meteor_runtime_config__ = JSON.parse(decodeURIComponent("%7B%22meteorRelease%22%3A%22METEOR%401.4.2.3%22%2C%22ROOT_URL_PATH_PREFIX%22%3A%22%22%2C%22meteorEnv%22%3A%7B%22NODE_ENV%22%3A%22production%22%7D%2C%22ROOT_URL%22%3A%22http%3A%2F%2Flocalhost%3A8080%22%7D"));</script>
        <script type="text/javascript" src="/undefined"></script>

        <meta charset="utf-8">
    <title>Project name</title>
    </head>
    <body>
    </body>
</html>

When changing index.html /undefined for /app.js I'm getting Uncaught ReferenceError: meteorInstall is not defined at app.js:1.

Am i missing something?

Thanks

1. Blaze does not output a body.html file into the build.
2. Adding the tag <meteor-bundled-js /> to the body of a blaze app will fail on compile:

=> Errors prevented startup:

   While processing files with templating-compiler (for target web.browser):
   client/main.html:14: Only certain elements like BR, HR, IMG, etc. (and foreign elements like SVG) are allowed to
   self-close
   ...<meteor-bundled-js />   <h1>Welcome to Me...
   ^

As a consequence, there is no way to add the scripts files for meteor projects.

Is it possible to use this tool to create static www folder for PhoneGap Build?
(and manually add phonegap.js into index.html before meteor's js)

Relative paths for linking the css and js files is necessary to let it run from the file:// protocol.
Absolut paths are necessary for when you rewrite URLs. This can also be solved by adding the <base href="/"> metatag.

we should have a option telling what to use.

Can not set empty path to make it relative. OS Windows 7 x64

Hello @frozeman i like the idea of your prpject and it seems it might do the trick for what i am trying to accomplish.im building a captive portal which should collect users'datas and store it into a collection. I need to be able to host on the router used the client part which will exchange with the meteor server part via meteor methods and which will be hosted on a remote server with docker..ive read the docs and some of the issues but i am a bit confused about how to handle the connections between client and server.could you please help me out?

In the command prompt not available meteor-build-client command
Maybe it's not installed, becouse no meteor_build_client catalog in node_modules directory on root of project.
can you help me?
sorry for my english

Hi,
Getting an error when trying to bundle sample meteor app, here are steps to reproduce it:
I'am on MacOS 10.10.3 , Node v0.10.36, Meteor 1.1.0.2

meteor create test-website
test-website: created.

To run your new app:
  cd test-website
  meteor
 ~/Projects 
» cd test-website
 ~/Projects/test-website 
» meteor-build-client ../myOutputFolder
Bundling app with Meteor...
Extracting the bundle...
|
stream.js:94
      throw er; // Unhandled stream error in pipe.
            ^
Error: ENOENT, lstat '/Users/su/Projects/myOutputFolder/app.tar.gz'

sudo meteor-build-client /Users/user/Desktop

My whole desktop got replaced with build files. No recovery :(
A warning would be nice.

disregard

If there is no CSS in a new project (if the file minifies to nothing) and you run meteor-build-client then it raises an error:

meteor-build-client ../test-meteor --path ''
Bundling Meteor app...
Generating the index.html...
path.js:488
      throw new TypeError('Arguments to path.join must be strings');
            ^
TypeError: Arguments to path.join must be strings
    at Object.posix.join (path.js:488:13)
    at Object.module.exports.addIndexFile (/usr/lib/node_modules/meteor-build-client/meteor.js:121:48)
    at /usr/lib/node_modules/meteor-build-client/main.js:79:20
    at null._onTimeout (/usr/lib/node_modules/meteor-build-client/queue.js:41:11)
    at Timer.listOnTimeout (timers.js:119:15)

I know this is ridiculously obscure, but it's possible if e.g. you are just trying out the system for the first time with a newly generated empty project.

I am getting errors with Meteor 1.3.1

I followed the instructions and get the index.html and js file. However, I get an error when I try to open the index.html file in Chrome.

Failed to load resource: net::ERR_FILE_NOT_FOUND
Uncaught TypeError: Cannot read property 'NODE_ENV' of undefined
Uncaught ReferenceError: Meteor is not defined

Two css files are being generated in the build output however the second is not being included in the generated index.html file.

Build output directory

index.html (the 5ac12377e86546bc57d1ae8dfa6b57a4aa491f15.css file is not being included)

<!DOCTYPE html>
<html>
    <head>
        <link rel="stylesheet" type="text/css" class="__meteor-css__" href="9be2645210ab06a7045a7c0455088fc9ffb667e1.css?meteor_css_resource=true">
        <script type="text/javascript">__meteor_runtime_config__ = JSON.parse(decodeURIComponent("%7B%22meteorRelease%22%3A%22METEOR%401.3.4.4%22%2C%22ROOT_URL_PATH_PREFIX%22%3A%22%22%2C%22meteorEnv%22%3A%7B%22NODE_ENV%22%3A%22production%22%7D%2C%22ROOT_URL%22%3A%22%22%2C%22PUBLIC_SETTINGS%22%3A%7B%22persistent_session%22%3A%7B%22default_method%22%3A%22persistent%22%7D%7D%7D"));</script>
        <script type="text/javascript" src="7c35bebebc60b49141ebf65f8f1ce4f0e3c5673f.js"></script>
        <script type="text/javascript">Meteor.disconnect();</script>
        <title>ProLease</title>
    <meta http-equiv="Content-Type" content="text/html;charset=utf-8" />
    <meta name="apple-mobile-web-app-capable" content="yes">
    <link rel="shortcut icon" href="/icons/favicon.ico" type="image/x-icon" />
    <link rel="apple-touch-icon" href="/images/appicons/apple-touch-icon.png" />
    <link rel="apple-touch-icon" sizes="57x57" href="/images/appicons/apple-touch-icon-57x57.png" />
    <link rel="apple-touch-icon" sizes="72x72" href="/images/appicons/apple-touch-icon-72x72.png" />
    <link rel="apple-touch-icon" sizes="76x76" href="/images/appicons/apple-touch-icon-76x76.png" />
    <link rel="apple-touch-icon" sizes="114x114" href="/images/appicons/apple-touch-icon-114x114.png" />
    <link rel="apple-touch-icon" sizes="120x120" href="/images/appicons/apple-touch-icon-120x120.png" />
    <link rel="apple-touch-icon" sizes="144x144" href="/images/appicons/apple-touch-icon-144x144.png" />
    <link rel="apple-touch-icon" sizes="152x152" href="/images/appicons/apple-touch-icon-152x152.png" />
    <meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=1, user-scalable=no">
    <link rel="stylesheet" href="fonts/calibri.css" >
    <link rel="stylesheet" href="icons/style.css" >
    <link rel="stylesheet" href="styles/style.css" >
    <link href="https://fonts.googleapis.com/css?family=Open+Sans" rel="stylesheet" type="text/css">
    <script src="scripts/director.min.js"></script>
    </head>
    <body>
    </body>
</html>

Running on [email protected]

Package versions:

[email protected]
[email protected]
[email protected]
[email protected]
[email protected]_1
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
clinical:[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
ecwyne:[email protected]
[email protected]
[email protected]
[email protected]
flawless:[email protected]
fortawesome:[email protected]
fourseven:[email protected]_1
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
lepozepo:[email protected]
[email protected]
[email protected]
lookback:[email protected]
[email protected]
[email protected]
meteorflux:[email protected]
meteorflux:[email protected]
[email protected]
[email protected]
[email protected]
mizzao:[email protected]
mizzao:[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
momentjs:[email protected]
[email protected]_1
[email protected]
[email protected]
oaf:[email protected]
[email protected]
[email protected]
[email protected]
raix:[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
remodal:[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
stevezhu:[email protected]
[email protected]
[email protected]
themeteorites:[email protected]
[email protected]
u2622:[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
webtempest:[email protected]

Greetings,
Probably to early for this one, but could you tell if your build tool will be compatible with Meteor 1.2 by default?

=λ meteor-build-client ../build
Bundling Meteor app...
Generating the index.html...
fs.js:500
  return binding.open(pathModule._makeLong(path), stringToFlags(flags), mode);
                 ^
Error: ENOENT, no such file or directory '../mmbldc/head.html'
    at Error (native)
    at Object.fs.openSync (fs.js:500:18)
    at Object.fs.readFileSync (fs.js:352:15)
    at Object.module.exports.addIndexFile (/usr/local/lib/node_modules/meteor-build-client/meteor.js:98:23)
    at /usr/local/lib/node_modules/meteor-build-client/main.js:79:20
    at null._onTimeout (/usr/local/lib/node_modules/meteor-build-client/queue.js:41:11)
    at Timer.listOnTimeout (timers.js:119:15)

Adding a try{}catch would fix it. I'll submit a pull soon.

...and titlefail 😅

I experimented with this package a few weeks ago running node v6.12.2 on OSX with a Meteor version of 1.3. I just updated to Meteor 1.6 and this package no longer works. It was working great before.

Not sure if the environment has changed on my Mac after the update. I tried it with the current node version, then again after using nvm to update to node v8.8.1, then again after reverting back to v6.12.2. I also tried the global install of the meteor-build-client package as well as with a local install.

I also found these issues: #19 and #4 so i tried both relative and absolute paths in my script. I get the same result every time I try to build.

I'm just running meteor-build-client ../client-build from the app directory. It used to work and generate the client-build folder as a sibling to /app.

I'm getting the star.json error and can't seem to get past it. Do you think this is an environment issue?

I should also add that after the build seems to have finished there is no client-build folder generated. This could be more the issue.

Here's the error, truncated.
Bundling Meteor app... Generating the index.html... { Error: Cannot find module '/Users/****/Sites/****/public_html/client-build/bundle/star.json' at Function.Module._resolveFilename (module.js:469:15) at Function.Module._load (module.js:417:25) at Module.require (module.js:497:17) at require (internal/module.js:20:19) ...

I'm running the following command to run a build

meteor-build-client ../build -p ""

When I check the console after uploading to my webserver I get the following:

Failed to load resource: the server responded with a status of 404 (Not Found) 
http://urltomysite.com/sockjs/info?cb=m69amdvokn

Hello,
Does Meteor-build-client work with the latest release of Meteor? I have used it successfully with Meteor 1.6 but not with Meteor 1.8.

Would this work for React meteor packages?

Please suggest me how get server URL dynamically at run time via server environment variable.

I am using git to track the output of meteor-build-client but the scripts and styles are changing file names each time the process runs. This means git thinks the prior version of the scripts are being deleted and the new files are being created / added.

Example:

02fa888b4b14f641de5add8c54923fefdb85c36f.js
737d4405b6d5123d24bbc1339055c0800a7406b4.css
index.html

... changing to:

05e746150274630cb5732dc013fbd08c7d262996.js
5cd04d43a893cab1c2c43355b3265eca8b063f94.css
index.html

(Git sees this as deleting the first files and adding the new, which means redundant data is being stored in the git repository)

Is there a way to use a common file name each time the build process is run instead of using a generated hash string?

Thank you.

I am building Chrome App and this module is perfect for it but question after building client how can i connect it back to the server.

I saw that you have provided an example :

DDPConnection = (Meteor.isClient) ? DDP.connect('http://localhost:3000/') : {};

if(Meteor.isClient) {
    // set the new DDP connection to all internal packages, which require one
    Meteor.connection = DDPConnection;
    Accounts.connection = Meteor.connection;
    Meteor.users = new Mongo.Collection('users');
    Meteor.connection.subscribe('users');
}

// When creating a collection use:
posts = new Mongo.Collection("posts", DDPConnection);
// And to subscribe use the DDP connection
DDPConnection.subscribe("mySubscription");

Question is where i need to place this ? can you show an example ?

Hi all, just a newbie question:
I'm trying

meteor-build-client ../dappfolder -p ""
getting four files:
a04db942e7de2b04c9b00de5bef17125c78658bb.css
index.html
e172b96067632038a7553b637811428b18c5c483.js
e172b96067632038a7553b637811428b18c5c483.stats.json

I can't get the "clear code" of e172b96067632038a7553b637811428b18c5c483.js , but something like:

!function(){var t,e,n;(function(){t=this}).call(this),function(){e=meteor_runtime_config.meteorEnv, ...
"undefined"==typeof Package&&(Package={}),Package["meteor-base"]={}; ...

How can I get the code of e172b96067632038a7553b637811428b18c5c483.js for a standalone, verifiable serverless application?

Thank you so much for your time and sorry for my poor english

How to reproduce the issue
[email protected]
[email protected]

Create blaze app: $ meteor create --blaze my-blaze-app
Build client: my-blaze-app$ meteor-build-client ../my-blaze-app-client-bundle

The generated client bundle contained a bundled css (c47dbe2a38954933b4ffc1fe3cf58f51146830bd.css) but did not include it in the generated index.html

How to fix the issue manually
Manually inserted <link rel="stylesheet" type="text/css" href="c47dbe2a38954933b4ffc1fe3cf58f51146830bd.css"> into index.html worked

Expected fix
I would expect the css be automatically included in the index.html by meteor-build-client.
I would also like to do a PR (because meteor-build-client is needed for our project) if some hints are given as where to start with.

If you do, we will be happy to continue your work.
@frozeman please, do not stay quiet.

Hey I'm working with this repository to export the meteor client of an app and inject it into a dom using a chrome extension. The build 2983439aeeb382.js file is throwing an error that it is not utf-8 encoded when trying to inject as a content script.

Is this a side effect of the meteor build itself or something I can be in control of with this build?

Thanks for your time.

Here:

Bundling Meteor app...
Generating the index.html...
module.js:338
    throw err;
    ^

Error: Cannot find module '/Users/lukeadams/Projects/belljar-io/Users/lukeadams/Desktop/buildtest/bundle/star.json'

It has to do with relative URL handling
PR incoming...

Just built this with Meteor 1.8.1 and a very simple standard repo (use meteor create) then built this using the manual form the README.

Build was fast and without errors and created a folder with the following files:

• index.html
• 524ea151167f0aa67862fb6b681b532466a7bc87.css
• c1e4e82dccf23c3809384659c50aa0177fedfcbe.js
• c1e4e82dccf23c3809384659c50aa0177fedfcbe.stats.json

However opening the index.html file locally caused the following error:

Loading failed for the <script> with source “file:///c1e4e82dccf23c3809384659c50aa0177fedfcbe.js”.
ReferenceError: Meteor is not defined

Edit: the above error occurred on FireFox, while Chrome gave me this output:

Failed to load resource: net::ERR_FILE_NOT_FOUND (c1e4e82dccf23c3809384659c50aa0177fedfcbe.js:1)
Failed to load resource: net::ERR_FILE_NOT_FOUND (/524ea151167f0aa67862fb6b681b532466a7bc87.css?meteor_css_resource=true:1)
Uncaught ReferenceError: Meteor is not defined
    at index.html:7 (index.html:7)

When I don't separate meteor from the client I access to multiple databases using

var database = new MongoInternals.RemoteCollectionDriver("<mongo url>");
MyCollection = new Mongo.Collection("collection_name", { _driver: database });

There is any way to access multiple databases from the client using meteor-build-client?
I have to create methods, or there is an easier way?

Hello! First I want to say that your package is awesome and has helped me a lot!

I encountered a minor bug when building for React. React needs its target to exist in the DOM. For example in my client/main.html file, I have this in the body:

<body>
    <div id="react-target"></div>
</body>

I added the react-target element to the build's index.html file and everything works fine.
FYI I'm running Meteor 1.8.1 and React 16.5.0

Thanks again!

Building my simple truffle / meteor project on my laptop takes > 30 seconds.

Is this expected, and is there anything I can do to improve the build time? I am on an old, low-ram laptop (4GB X200 w/Debian Jessie) but this still seems slow.

Hello there,

Great tool, I'm using it a lot, thank you for all work you have done.

I have a question regarding this line. While it is used in case when it served by Meteor app, see this lines and note it's absolutely useless to use meteor_css_resource for server-less solution. Moreover it get query may prevent proxy-caching in some cases.

At the same time meteor_js_resource for <script> is not appended, see it in Meteor core

If you agree with my point - I may send a PR

On Windows, does it uses all the same feature in this meteor build client including the ability to reload page when it detect code change?

Actually I am using your package to build my meteor client application. if I had provided meteor server URL at build time then it works fine, but I want to give meteor server URL at run time dynamically (ex. environment variable) then Is any way to do this thing?
Its required because we have two Meteor admin servers and I want, when I change URL path of my client app hosted server environment variable, My meteor Client app redirect and connect with other server.

The problem

When executing meteor-build-client ../ in de Meteor application folder. It deletes everything. Looking at the code, this makes sense. But when you want to export the static files one folder higher, it's unexpected behavior and can even cause users to lose all their work.

Steps to reproduce

• Create a folder called foo/ and cd into it.

• meteor create app

• cd app

• meteor-build-client ../

• You get the following error:

  Bundling Meteor app...
  
  fs.js:612
    return binding.rmdir(pathModule._makeLong(path));
                   ^
  Error: ENOENT, no such file or directory './../'
      at Object.fs.rmdirSync (fs.js:612:18)
      at deleteFolderRecursive (/usr/local/lib/node_modules/meteor-build-client/meteor.js:48:12)
      at Object.module.exports.build (/usr/local/lib/node_modules/meteor-build-client/meteor.js:56:9)
      at /usr/local/lib/node_modules/meteor-build-client/main.js:68:20
      at null._onTimeout (/usr/local/lib/node_modules/meteor-build-client/queue.js:41:11)
      at Timer.listOnTimeout [as ontimeout] (timers.js:110:15)

  And the foo/ folder is completely empty.

In this scenario the user would lose all files inside foo/, including the folder where the Meteor application is located. This should be fixed.

The dynamic-import package does not work with a client-only app, so we need to bundle all imports while building statically.

A similar approach is done by bundle-visualizer. I could provide a PR if there is some alive-ping.