i`m using Meteor 1.6. with coffeescript package and when i use 'import' to import npm package, i have this error.
Errors prevented startup:
While processing files with coffeescript (for target web.browser):
client/pages/list/itemsList.coffee:1:1: reserved word 'import'
Here my packages file:
meteor-base#1.3.0 # Packages every Meteor app needs to have
mobile-experience#1.0.5 # Packages for a great mobile UX
mongo#1.4.2 # The database Meteor supports right now
blaze-html-templates#1.0.4 # Compile .html files into Meteor Blaze views
reactive-var#1.0.11 # Reactive variable for tracker
tracker#1.1.3 # Meteor's client-side reactive programming library
coffeescript
dynamic-import
standard-minifier-css#1.4.0 # CSS minifier run for production mode
standard-minifier-js#2.3.1 # JS minifier run for production mode
es5-shim#4.7.0 # ECMAScript 5 compatibility for older browsers
shell-server#0.3.1 # Server-side component of the `meteor shell` command
ecmascript
check
ejson
jquery
less
random
rate-limit
yasaricli:slugify
kadira:flow-router
kadira:blaze-layout
momentjs:moment
accounts-base
accounts-ui
accounts-password
service-configuration
accounts-facebook
session
http
email
patrickml:swal
raix:handlebar-helpers
ostrio:files
ethereum:web3
tap:i18n
meteorhacks:ssr
Please, help. I don`t know what to do.. I have latest updated coffeescript and ecmascript packages.
Update:
after meteor update i have this result
The following top-level dependencies were not updated to the very latest
version available:
* coffeescript 1.0.17 (2.2.1_1 is available)
Solved:
This is due to the package tap:i18n it has in the dependencies is such a version of coffeescript
You also need the modules package.
meteor add modules
Related
When I install chai-http it warns that formidable 1.2.6 is deprecated, and even though this is a dev dependency, when I push to my server the node app fails when asking it to npm install.
formidable is actually a dependency of superagent
I've tried updating chai-http, superagent and formidable, but my package.lock.json reference of "formidable": "^1.2.0", never gets updated.
npm outdated --depth=5 doesn't show me formidable as being installed but its in my package.lock.json under superagent, and that's where the error log points.
At present my workaround is to remove chai-http before pushing to server.
How can I update the formidable module?
I am new to meteor iron and I am trying to install aldeed collection2 but the app is crushing
W20190215-12:44:48.023(2)? (STDERR) WARNING: npm peer requirements (for aldeed:collection2) not installed:
W20190215-12:44:48.024(2)? (STDERR) - simpl-schema#>=0.0.0 not installed.
I have tried to install simple-schema but nothing is working.
meteor npm install simpl-schema --save
I have also removed and reinstalled collection2 but I still get the same error. What is it that I am missing?
I tried to reproduce the error with a new created repo, that contains the dependencies you have listed but everything runs fine on my side.
However, I found, thataldeed:collection2-core is now somewhat deprecated and being merged back into aldeed:collection2 as you can read in the project repository on GitHub:
MPORTANT: This package has been merged back into aldeed:collection2 as version 3.0.0 of that package. Refer to https://github.com/aldeed/meteor-collection2/blob/master/CHANGELOG.md#300
Create issues and PRs in the other repo going forward: https://github.com/aldeed/meteor-collection2/issues
Issues remain enabled on this repo for reference to existing issues only.
So a good first step would be to remove the deprecated package and install the updated one:
meteor remove aldeed:collection2-core
meteor add aldeed:collection2
If you want to start from a new clean project you can reproduce these steps to get to a running starting point here:
meteor create someprojectname
cd someprojectname
meteor add iron:router twbs:bootstrap aldeed:autoform aldeed:collection2
meteor npm install --save iron simpl-schema
meteor
The project will start without errors. From here you can start including your former code and see if the error will come back (which is then likely to be an issue inside your code) or not.
Important note on twbs:bootstrap:
The package twbs:bootstrap is using an old version (3.3.6) which is considered to contain several security vulnerabilities (read here and here).
If you want to use the latest Bootstrap you may rather install bootstrap using npm like so:
meteor remove twbs:bootstrap
meteor npm install --save bootstrap#latest jquery#latest popper.js#latest
You need jquery here, too because Meteor does not contain the required version and popper.js handles the Popover, Modal etc.
To include it in your code you need to add these lines to your client code:
import 'bootstrap'
import popper from 'popper.js'
global.Popper = popper
To use Bootstrap 4 with AutoForm you can install imajus:autoform-bootstrap4 (repo) and add the following to your client code:
AutoForm.setDefaultTemplate('bootstrap4')
With 1.2.*, I used to build my staging/production bundles with meteor build, then moving into ./bundle/programs/server and npm install there.
I do the same thing with 1.3 version but now I have error message on trying to run bundle main file with node:
WARNING: npm peer requirements not installed:
- react#0.14.x not installed.
- react-addons-pure-render-mixin#0.14.x not installed.
Read more about installing npm peer dependencies:
http://guide.meteor.com/using-packages.html#peer-npm-dependencies
/var/www/builds/1459320997/bundle/programs/server/node_modules/fibers/future.js:267
throw(ex);
^
Error: Can't find npm module 'react'. Did you forget to call 'Npm.depends' in package.js within the 'modules-runtime' package?
I use react-meteor-data meteor package.
However, I already have "react": "^0.14.8", and "react-addons-linked-state-mixin": "^0.14.8", in my package.json and of course installed it with npm install ... --save and it is working fine on development environment when I use meteor command.
Any additional actions needed to run it? Did they change how meteor package should be build for production and didn't changed their docs? (because I don't see any changes in docs concerning meteor build so far.
Update: I tried to manually npm install these packages into ./bundle/program/server. Now they consequentially requires packages already listed in my package.json. I suppose Meteor just ignore this file on bundle. Will try to add a bug in their tracker.
I used Meteor 1.2 to build new 1.3 code so it is the issue. It happened because currently I build on the server that had another Meteor version.
I used answer from another Stackoverflow user (Ian) Updating all Meteor packages to latest versions
Easiest way is to delete the contents of .meteor/versions and then save
I'm running into the below issues when I upgraded my meteor project from 1.1.6 to 1.2.0.2:
> Uncaught ReferenceError: SimpleSchema is not defined Uncaught
> ReferenceError: AccountsTemplates is not defined Uncaught
> ReferenceError: Meteor is not defined Uncaught ReferenceError:
> Template is not defined
It is successful project deployed using 1.1.6
I'm not sure how to fix this, please suggest.
Thanks.
The below is my packages files:
# Meteor packages used by this project, one per line.
# Check this file (and the other files in this directory) into your repository.
#
# 'meteor add' and 'meteor remove' will edit this file for you,
# but you can also edit it by hand.
meteor-base # Packages every Meteor app needs to have
mobile-experience # Packages for a great mobile UX
mongo # The database Meteor supports right now
blaze-html-templates # Compile .html files into Meteor Blaze views
session # Client-side reactive dictionary for your app
jquery # Helpful client-side library
tracker # Meteor's client-side reactive programming library
logging
reload
random
ejson
check
standard-minifiers # JS/CSS minifiers run for production mode
es5-shim # ECMAScript 5 compatibility for older browsers.
ecmascript # Enable ECMAScript2015+ syntax in app code
underscore
iron:router
spacebars
less
materialize:materialize
useraccounts:materialize
useraccounts:core
aldeed:collection2
aldeed:autoform
gildaspk:autoform-materialize
accounts-password
alethes:pages
matb33:collection-hooks
alanning:roles
meteorhacks:aggregate
momentjs:moment
pcel:serialize
pcel:loading
aldeed:simple-schema
digilord:faker
meteorhacks:kadira
useraccounts:flow-routing
I have a meteor iron app I generated. In the eventedmind screencast the instructor searches packages with iron search ^accounts to see all meteor packages. When I run that though
$ iron search ^accounts
> meteor search app bin build config readme.md
How can I search for meteor packages with the iron command line tool? I'm using iron-meteor version 1.1.2
you don't need iron to search meteor packages. Use meteor search:
meteor search sometext